`cryptoboss340.top`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::6815:3f07^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:a8f7^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.63.7^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.168.247^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`casey.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c9e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c39e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`casey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:239e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`casey.ns.cloudflare.com`
		A	108.162.195.158^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
		A	162.159.44.158^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
		A	172.64.35.158^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`casey.ns.cloudflare.com`
NS	`dell.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a5e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dell.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c05e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`dell.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:205e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`dell.ns.cloudflare.com`
		A	108.162.192.94^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dell.ns.cloudflare.com`
		A	172.64.32.94^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dell.ns.cloudflare.com`
		A	173.245.58.94^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`dell.ns.cloudflare.com`
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`
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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
TXT	`yandex-verification: 9196a548141f4424`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.63.7, 172.67.168.247
		IPv6	2606:4700:3035::6815:3f07, 2606:4700:3037::ac43:a8f7
SOA	`casey.ns.cloudflare.com`dns@cloudflare.com serial=2397177278

`top`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.zdnscloud.com` ⭐
	NS	`a.zdnscloud.cn`
	NS	`b.zdnscloud.cn`
	NS	`c.zdnscloud.com`
	NS	`d.zdnscloud.com`
	NS	`f.zdnscloud.cn`
	NS	`g.zdnscloud.com`
	NS	`i.zdnscloud.cn`
	NS	`j.zdnscloud.com`
	TXT	`2026-03-25_20:40:02`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1395357442

Same first word

cryptoboss340.top

DNS History

9 records (9 active, 0 former)

●NScasey.ns.cloudflare.com2026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●NSdell.ns.cloudflare.com2026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●MXroute1.mx.cloudflare.net2026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●MXroute2.mx.cloudflare.net2026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●MXroute3.mx.cloudflare.net2026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●A104.21.63.72026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●A172.67.168.2472026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●A2606:4700:3035::6815:3f072026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

●A2606:4700:3037::ac43:a8f72026-03-02 → 2026-03-25 · 2 obs

● 2026-03-02 06:26:04
● 2026-03-25 13:02:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
top	c.zdnscloud.com, f.zdnscloud.cn, a.zdnscloud.cn, g.zdnscloud.com...	8 records
cryptoboss340.top	dell.ns.cloudflare.com, casey.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.94

NS records: dell.ns.cloudflare.com, casey.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cryptoboss340.top (unsigned zone)

⏱️ Timing

Total: 996ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.168.247, 104.21.63.7`
AAAA	2	`2606:4700:3035::6815:3f07, 2606:4700:3037::ac43:a8f7`
NS	2	`casey.ns.cloudflare.com, dell.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 54), route1.mx.cloudflare.net (pri: 88)...`
TXT	2	`v=spf1 include:_spf.mx.cloudflare.net ~a, yandex-verification: 9196a548141f4424`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`casey.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (c.zdnscloud.com, f.zdnscloud.cn, a.zdnscloud.cn...)

Analysis

IP Addresses

cryptoboss340.top points to four IP numbers: 2606:4700:3035::6815:3f07, 2606:4700:3037::ac43:a8f7, 104.21.63.7 and 172.67.168.247.

For instance, other host names mesulaj.com, dizibaba.com, thehercules.co.uk, gxnnls.cn and coastal-awakening.com share IP numbers with cryptoboss340.top.

Name Servers

cryptoboss340.top is delegated to two name servers: casey.ns.cloudflare.com and dell.ns.cloudflare.com.

cryptoboss340.top uses the same name server setup as other domains such as theministryofphotography.co.uk, rozumnadytyna.com.ua, stoodydom.fr, picton-castle.com and kumcams.com.

cryptoboss340.top shares name servers with other domains at least partially, for example sxkis.cn, movieply.com, jclgps.com, luckyroll1.click and theamazingseries.com.

These name servers are commonly used with the name servers kim.ns.cloudflare.com and tori.ns.cloudflare.com.

Host names with six IP numbers: host name casey.ns.cloudflare.com points to: 2606:4700:58::a29f:2c9e, 2803:f800:50::6ca2:c39e, 2a06:98c1:50::ac40:239e, 108.162.195.158, 162.159.44.158 and 172.64.35.158; host name dell.ns.cloudflare.com points to: 2606:4700:50::adf5:3a5e, 2803:f800:50::6ca2:c05e, 2a06:98c1:50::ac40:205e, 108.162.192.94, 172.64.32.94 and 173.245.58.94.

Mail Servers

cryptoboss340.top is served by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

cryptoboss340.top shares mail servers with other domains at least partially; for instance scotthu.com, landsharklabs.com, oemails.com, bestalltop.com and ielev8cs.com.

Host names with six IP numbers:

route1.mx.cloudflare.net points to 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13.

route2.mx.cloudflare.net points to 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19.

route3.mx.cloudflare.net points to 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

cryptoboss340.top - robtex.com