trydataforgecrew.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`trydataforgecrew.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:2f9c^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:94de^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.47.156^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.148.222^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`pearl.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:268c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c28c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`pearl.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:228c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`pearl.ns.cloudflare.com`
		A	108.162.194.140^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	162.159.38.140^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
		A	172.64.34.140^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pearl.ns.cloudflare.com`
NS	`peter.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c03^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peter.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c303^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`peter.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2303^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`peter.ns.cloudflare.com`
		A	108.162.195.3^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peter.ns.cloudflare.com`
		A	162.159.44.3^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peter.ns.cloudflare.com`
		A	172.64.35.3^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peter.ns.cloudflare.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4023:2009::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxer-in-f26.1e100.net`
		A	2607:f8b0:4023:2009::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxer-in-f27.1e100.net`
		A	2607:f8b0:4023:200b::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxej-in-f26.1e100.net`
		A	2607:f8b0:4023:200b::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yuphxej-in-f27.1e100.net`
		A	172.217.75.26^{🇺🇸 Google172.217.75.0/24}
			PTR	`yuphxej-in-f26.1e100.net`
		A	172.217.75.27^{🇺🇸 Google172.217.75.0/24}
			PTR	`yuphxej-in-f27.1e100.net`
		A	192.178.164.26^{🇺🇸 Google192.178.164.0/24}
			PTR	`yuphxer-in-f26.1e100.net`
		A	192.178.164.27^{🇺🇸 Google192.178.164.0/24}
			PTR	`yuphxer-in-f27.1e100.net`
		A	192.179.30.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`yuphxug-in-f27.1e100.net`
TXT	`google-site-verification=pL2y-zQcSQm_ye3R6Vg-CSeCTWKkAuSBQaqdEWaXpZM`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.47.156, 172.67.148.222
		IPv6 hints	2606:4700:3032::6815:2f9c, 2606:4700:3037::ac43:94de
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=36, name=cloudflare-ech.com
SOA	`pearl.ns.cloudflare.com`dns@cloudflare.com serial=2417356712

`com`

	DNSSEC	⚠️ Not signed
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1793987061

Same first word

trydataforgecrew.com

Previous names

Next names

DNS History

11 records (7 active, 4 former)

●NSpearl.ns.cloudflare.com2026-08-18 → 2026-11-06 · 2 obs

● 2026-08-18 14:16:10
● 2026-11-06 18:17:10

●NSpeter.ns.cloudflare.com2026-08-18 → 2026-11-06 · 2 obs

● 2026-08-18 14:16:10
● 2026-11-06 18:17:10

●MXsmtp.google.com2026-08-18 → 2026-11-06 · 2 obs

● 2026-08-18 14:16:10
● 2026-11-06 18:17:10

●A104.21.47.1562026-10-31 → 2026-11-06 · 3 obs

○ 2026-08-18 14:16:10
● 2026-10-31 03:15:54
● 2026-11-06 18:17:10

●A172.67.148.2222026-10-31 → 2026-11-06 · 3 obs

○ 2026-08-18 14:16:10
● 2026-10-31 03:15:54
● 2026-11-06 18:17:10

○A188.114.96.02026-08-18 → 2026-08-18 · 3 obs

● 2026-08-18 14:16:10
○ 2026-10-31 03:15:54
○ 2026-11-06 18:17:10

○A188.114.97.02026-08-18 → 2026-08-18 · 3 obs

● 2026-08-18 14:16:10
○ 2026-10-31 03:15:54
○ 2026-11-06 18:17:10

●A2606:4700:3032::6815:2f9c2026-10-31 → 2026-11-06 · 3 obs

○ 2026-08-18 14:16:10
● 2026-10-31 03:15:54
● 2026-11-06 18:17:10

●A2606:4700:3037::ac43:94de2026-10-31 → 2026-11-06 · 3 obs

○ 2026-08-18 14:16:10
● 2026-10-31 03:15:54
● 2026-11-06 18:17:10

○A2a06:98c1:3120::2026-08-18 → 2026-08-18 · 3 obs

● 2026-08-18 14:16:10
○ 2026-10-31 03:15:54
○ 2026-11-06 18:17:10

○A2a06:98c1:3121::2026-08-18 → 2026-08-18 · 3 obs

● 2026-08-18 14:16:10
○ 2026-10-31 03:15:54
○ 2026-11-06 18:17:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
trydataforgecrew.com	pearl.ns.cloudflare.com, peter.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.140

NS records: pearl.ns.cloudflare.com, peter.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 241ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.148.222, 104.21.47.156`
AAAA	2	`2606:4700:3037::ac43:94de, 2606:4700:3032::6815:2f9c`
NS	2	`pearl.ns.cloudflare.com, peter.ns.cloudflare.com`
MX	1	`smtp.google.com (pri: 1)`
TXT	2	`google-site-verification=pL2y-zQcSQm_ye3, v=spf1 include:_spf.google.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`pearl.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (pearl.ns.cloudflare.com, pearl.ns.cloudflare.com, pearl.ns.cloudflare.com...)

Analysis

IP Addresses

trydataforgecrew.com points to the four IP addresses 104.21.47.156, 172.67.148.222, 2606:4700:3032::6815:2f9c and 2606:4700:3037::ac43:94de.

londonuktouristguide.com, youseffarge.com, dianewyatt.tk plus two other host names have IP numbers in common with trydataforgecrew.com.

Name Servers

Two name servers handle the delegation for trydataforgecrew.com: pearl.ns.cloudflare.com and peter.ns.cloudflare.com.

The name server configuration of trydataforgecrew.com is shared with other domains, for instance naspen.net, markmerch.info, elevatewendtpartners.com and two others.

There is at least partial name server overlap between trydataforgecrew.com and other domains — hartschalenkoffer.shop, cashflowinsights.it, bigbox.lt and two more among them.

These name servers are routinely deployed together with the name servers kai.ns.cloudflare.com.

Hosts with 6 IP addresses each:

pearl.ns.cloudflare.com resolves to 108.162.194.140, 162.159.38.140 and 172.64.34.140 among others, with 3 other IP addresses in total.

peter.ns.cloudflare.com resolves to 108.162.195.3, 162.159.44.3 and 172.64.35.3 among others, with 3 other IP addresses in total.

Mail Servers

trydataforgecrew.com uses one mail server — smtp.google.com.

The mail server setup of trydataforgecrew.com matches that of other domains such as catch22properties.com, faerabloom.com, terrefranche.com and two others.

At least some of the mail servers used by trydataforgecrew.com are shared with other domains: thepurplesquirrel.io, cvru.ac.in, earthorganization.com and two others among them.

smtp.google.com has 9 IP addresses: 172.217.75.26, 172.217.75.27, 192.178.164.26 plus 6 more.