🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`pullstring.app`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::6815:f74^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::ac43:a293^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.15.116^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.162.147^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`bailey.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2629^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bailey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c229^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`bailey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2229^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`bailey.ns.cloudflare.com`
		A	108.162.194.41^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bailey.ns.cloudflare.com`
		A	162.159.38.41^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bailey.ns.cloudflare.com`
		A	172.64.34.41^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`bailey.ns.cloudflare.com`
NS	`jake.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b7a^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jake.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c17a^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jake.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:217a^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jake.ns.cloudflare.com`
		A	108.162.193.122^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jake.ns.cloudflare.com`
		A	172.64.33.122^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jake.ns.cloudflare.com`
		A	173.245.59.122^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jake.ns.cloudflare.com`
MX	`route2.mx.cloudflare.net` ⭐
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁵¹⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁶⁶⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
TXT	`google-site-verification=xNclIcCwGsfmXdKxLliFfzx5_J4yw1phDaTanBd1ipg`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.15.116, 172.67.162.147
		IPv6 hints	2606:4700:3035::6815:f74, 2606:4700:3035::ac43:a293
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=43, name=cloudflare-ech.com
SOA	`bailey.ns.cloudflare.com`dns@cloudflare.com serial=2419151417

`app`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=101427

🔒 HSTS Preload (+subdomains)

Same first word

pullstring.ai

pullstring.org

pullstring.ph

pullstring.com.ph

pullstring.studio

pullstring.net

pullstring.app

pullstring.com

pullstring.co

Similar names

stringpull.com

Previous names

Next names

DNS History

9 records (9 active, 0 former)

●NSbailey.ns.cloudflare.com2026-10-18 → 2026-11-12 · 2 obs

● 2026-10-18 10:15:20
● 2026-11-12 00:01:56

●NSjake.ns.cloudflare.com2026-10-18 → 2026-11-12 · 2 obs

● 2026-10-18 10:15:20
● 2026-11-12 00:01:56

●MXroute1.mx.cloudflare.net2026-11-11 → 2026-11-12 · 2 obs

● 2026-11-11 23:55:28
● 2026-11-12 00:01:56

●MXroute2.mx.cloudflare.net2026-11-11 → 2026-11-12 · 2 obs

● 2026-11-11 23:55:28
● 2026-11-12 00:01:56

●MXroute3.mx.cloudflare.net2026-11-11 → 2026-11-12 · 2 obs

● 2026-11-11 23:55:28
● 2026-11-12 00:01:56

●A104.21.15.1162026-10-18 → 2026-11-12 · 2 obs

● 2026-10-18 10:15:20
● 2026-11-12 00:01:56

●A172.67.162.1472026-10-18 → 2026-11-12 · 2 obs

● 2026-10-18 10:15:20
● 2026-11-12 00:01:56

●A2606:4700:3035::6815:f742026-10-18 → 2026-11-12 · 2 obs

● 2026-10-18 10:15:20
● 2026-11-12 00:01:56

●A2606:4700:3035::ac43:a2932026-10-18 → 2026-11-12 · 2 obs

● 2026-10-18 10:15:20
● 2026-11-12 00:01:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com...	-
pullstring.app	jake.ns.cloudflare.com, bailey.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.122

NS records: jake.ns.cloudflare.com, bailey.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pullstring.app (unsigned zone)

⏱️ Timing

Total: 759ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.15.116, 172.67.162.147`
AAAA	2	`2606:4700:3035::ac43:a293, 2606:4700:3035::6815:f74`
NS	2	`bailey.ns.cloudflare.com, jake.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 24), route3.mx.cloudflare.net (pri: 51)...`
TXT	2	`google-site-verification=xNclIcCwGsfmXdK, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`bailey.ns.cloudflare.com dns.cloudflare.`

Analysis

IP Addresses

pullstring.app directs to four IP numbers, which are 104.21.15.116, 172.67.162.147, 2606:4700:3035::6815:f74 and 2606:4700:3035::ac43:a293.

Two other host names, along with trpg-setro.com, beyazsarayltd.com and conservative.today, also share IP numbers with pullstring.app.

Name Servers

pullstring.app uses two name servers for its delegation: bailey.ns.cloudflare.com and jake.ns.cloudflare.com.

pullstring.app shares its NS records with other domains, for example klungo.dev, winonahodeana.pages.dev, geospatialsoftware.com and two others.

The name servers of pullstring.app overlap at least partially with those of other domains — among them designloyal.com, techpaymentedge.com, tlb001.pages.dev and two more.

DNS names with 6 IP addresses:

Hostname bailey.ns.cloudflare.com directs to 108.162.194.41, 162.159.38.41 and 172.64.34.41 along with 3 other IP addresses.

Hostname jake.ns.cloudflare.com directs to 108.162.193.122, 172.64.33.122 and 173.245.59.122 along with 3 other IP addresses.

Mail Servers

Mail for pullstring.app is routed through three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

There is at least a partial MX overlap between pullstring.app and other domains, including 404exe.com, assayer.dev, custexiexianhai.store and two others.

DNS names with 6 IP addresses:

Hostname route1.mx.cloudflare.net directs to 162.159.205.11, 162.159.205.12 and 162.159.205.13 along with 3 other IP addresses.

Hostname route2.mx.cloudflare.net directs to 162.159.205.17, 162.159.205.18 and 162.159.205.19 along with 3 other IP addresses.

Hostname route3.mx.cloudflare.net directs to 162.159.205.23, 162.159.205.24 and 162.159.205.25 along with 3 other IP addresses.

pullstring.app - robtex.com

pullstring.app

app

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`pullstring.app`

`app`