`cryptoboss-lam.top`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:41d8^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:a76a^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.65.216^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.167.106^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`rory.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2ca6^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rory.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3a6^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rory.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23a6^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rory.ns.cloudflare.com`
		A	108.162.195.166^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rory.ns.cloudflare.com`
		A	162.159.44.166^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rory.ns.cloudflare.com`
		A	172.64.35.166^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rory.ns.cloudflare.com`
NS	`sima.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ade^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sima.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0de^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sima.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20de^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sima.ns.cloudflare.com`
		A	108.162.192.222^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sima.ns.cloudflare.com`
		A	172.64.32.222^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sima.ns.cloudflare.com`
		A	173.245.58.222^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sima.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: d636d3b2bd4f9eb7`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.65.216, 172.67.167.106
		IPv6 hints	2606:4700:3030::6815:41d8, 2606:4700:3033::ac43:a76a
SOA	`rory.ns.cloudflare.com`dns@cloudflare.com serial=2399598395

`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	`e.zdnscloud.cn`
	NS	`f.zdnscloud.cn`
	NS	`i.zdnscloud.cn`
	NS	`j.zdnscloud.com`
	TXT	`2026-05-14_11:05:01`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1395807219

rank #491445 globally
rank #2987 in the tld

Same first word

cryptoboss-lam.top

DNS History

9 records (9 active, 0 former)

●NSrory.ns.cloudflare.com2026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●NSsima.ns.cloudflare.com2026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●MXroute1.mx.cloudflare.net2026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●MXroute2.mx.cloudflare.net2026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●MXroute3.mx.cloudflare.net2026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●A104.21.65.2162026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●A172.67.167.1062026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●A2606:4700:3030::6815:41d82026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

●A2606:4700:3033::ac43:a76a2026-03-28 → 2026-05-14 · 2 obs

● 2026-03-28 23:12:10
● 2026-05-14 03:14:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
top	a.zdnscloud.cn, f.zdnscloud.cn, c.zdnscloud.com, e.zdnscloud.cn...	-
cryptoboss-lam.top	rory.ns.cloudflare.com, sima.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.195.166

NS records: rory.ns.cloudflare.com, sima.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cryptoboss-lam.top (unsigned zone)

⏱️ Timing

Total: 199ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.167.106, 104.21.65.216`
AAAA	2	`2606:4700:3033::ac43:a76a, 2606:4700:3030::6815:41d8`
NS	2	`rory.ns.cloudflare.com, sima.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: d636d3b2bd4f9eb7`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`rory.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

cryptoboss-lam.top points to four IP numbers: 2606:4700:3030::6815:41d8, 2606:4700:3033::ac43:a76a, 104.21.65.216 and 172.67.167.106.

Other host names, for instance cosmo4dset.top, dhxdemo.com, sabushpilot.com, divesmartgozo.com and durbanpersonals.co.za share IP numbers with cryptoboss-lam.top.

Name Servers

cryptoboss-lam.top's delegation is to two name servers rory.ns.cloudflare.com and sima.ns.cloudflare.com.

cryptoboss-lam.top shares the same name server configuration as other domains, such as balljad.me.uk, bitzap.ai, mercurytaxis.com, brillenmarkt.be and cryptoboss-lop.top.

cryptoboss-lam.top at least partially shares its name servers with other domains, for instance flashyred.com, hersonissos.ru, manaratelmostaqbal.com, theplasticbagcompany.co.uk and nationalsubsidyhelp.com.

These name servers are often used together with the name servers paige.ns.cloudflare.com.

Host names with six IP numbers:

rory.ns.cloudflare.com points to: 2606:4700:58::a29f:2ca6, 2803:f800:50::6ca2:c3a6, 2a06:98c1:50::ac40:23a6, 108.162.195.166, 162.159.44.166 and 172.64.35.166.

sima.ns.cloudflare.com points to: 2606:4700:50::adf5:3ade, 2803:f800:50::6ca2:c0de, 2a06:98c1:50::ac40:20de, 108.162.192.222, 172.64.32.222 and 173.245.58.222.

Mail Servers

cryptoboss-lam.top is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

cryptoboss-lam.top shares some mail servers with other domains, including qiuzao.com, laincubadora.biz, tinkerdifferent.com, 0t0.top and edusch.site.

Host names with six IP numbers:

route1.mx.cloudflare.net has IPs 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 has IPs 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 has IPs 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.

cryptoboss-lam.top - robtex.com