`crypto-frontier.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::6815:3059^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:b70a^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.48.89^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.183.10^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`jim.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b7d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c17d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jim.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:217d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jim.ns.cloudflare.com`
		A	108.162.193.125^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
		A	172.64.33.125^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
		A	173.245.59.125^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jim.ns.cloudflare.com`
NS	`laylah.ns.cloudflare.com`
		A	2606:4700:50::a29f:26e6^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`laylah.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2e6^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`laylah.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22e6^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`laylah.ns.cloudflare.com`
		A	108.162.194.230^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`laylah.ns.cloudflare.com`
		A	162.159.38.230^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`laylah.ns.cloudflare.com`
		A	172.64.34.230^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`laylah.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.48.89, 172.67.183.10
		IPv6 hints	2606:4700:3033::6815:3059, 2606:4700:3037::ac43:b70a
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=77, name=cloudflare-ech.com
SOA	`jim.ns.cloudflare.com`dns@cloudflare.com serial=2403182436

`com`

	DNSSEC	🔒 Signed (DS record present)
	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=1778305241

⚠️ On DNS blocklist: tif

Same first word

crypto-frontier.com

DNS History

6 records (6 active, 0 former)

●NSjim.ns.cloudflare.com2026-05-06 → 2026-05-09 · 2 obs

● 2026-05-06 22:55:10
● 2026-05-09 06:06:02

●NSlaylah.ns.cloudflare.com2026-05-06 → 2026-05-09 · 2 obs

● 2026-05-06 22:55:10
● 2026-05-09 06:06:02

●A104.21.48.892026-05-06 → 2026-05-09 · 2 obs

● 2026-05-06 22:55:10
● 2026-05-09 06:06:02

●A172.67.183.102026-05-06 → 2026-05-09 · 2 obs

● 2026-05-06 22:55:10
● 2026-05-09 06:06:02

●A2606:4700:3033::6815:30592026-05-06 → 2026-05-09 · 2 obs

● 2026-05-06 22:55:10
● 2026-05-09 06:06:02

●A2606:4700:3037::ac43:b70a2026-05-06 → 2026-05-09 · 2 obs

● 2026-05-06 22:55:10
● 2026-05-09 06:06:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net...	-
crypto-frontier.com	jim.ns.cloudflare.com, laylah.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.230

NS records: jim.ns.cloudflare.com, laylah.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for crypto-frontier.com (unsigned zone)

⏱️ Timing

Total: 109ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.183.10, 104.21.48.89`
AAAA	2	`2606:4700:3033::6815:3059, 2606:4700:3037::ac43:b70a`
NS	2	`jim.ns.cloudflare.com, laylah.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`jim.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

crypto-frontier.com resolves to four IPs: 2606:4700:3033::6815:3059, 2606:4700:3037::ac43:b70a, 104.21.48.89 and 172.67.183.10.

Other host names, for instance zt-chem.com, dlaczego.org.pl, dilmah.pl, www.bestboston.com and www.sem-experimentation.ch share IP numbers with crypto-frontier.com.

Name Servers

crypto-frontier.com has two name servers: jim.ns.cloudflare.com and laylah.ns.cloudflare.com.

crypto-frontier.com shares the same name server setup as other domains, for example pmatchinghotel.com, marblewavebase.garden, pylonstaticnet.garden, hashkey-hk.vip and cryptoonchains.cc.

crypto-frontier.com shares some name servers with other domains, for example justask.me, hireageekmail.com, ddrwg.com, mys--lady-romance.com and glasta.com.

These name servers are commonly used alongside colin.ns.cloudflare.com, simon.ns.cloudflare.com, eric.ns.cloudflare.com and pat.ns.cloudflare.com.

Host names with six IP numbers: jim.ns.cloudflare.com points to: 2606:4700:58::adf5:3b7d, 2803:f800:50::6ca2:c17d, 2a06:98c1:50::ac40:217d, 108.162.193.125, 172.64.33.125 and 173.245.59.125; laylah.ns.cloudflare.com points to: 2606:4700:50::a29f:26e6, 2803:f800:50::6ca2:c2e6, 2a06:98c1:50::ac40:22e6, 108.162.194.230, 162.159.38.230 and 172.64.34.230.

crypto-frontier.com - robtex.com