`track-map-device.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:4aee^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::ac43:a4a3^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.74.238^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.164.163^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`jimmy.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c4c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jimmy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c34c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jimmy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:234c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jimmy.ns.cloudflare.com`
		A	108.162.195.76^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jimmy.ns.cloudflare.com`
		A	162.159.44.76^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jimmy.ns.cloudflare.com`
		A	172.64.35.76^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jimmy.ns.cloudflare.com`
NS	`meadow.ns.cloudflare.com`
		A	2606:4700:50::a29f:2633^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meadow.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c233^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`meadow.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2233^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`meadow.ns.cloudflare.com`
		A	108.162.194.51^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meadow.ns.cloudflare.com`
		A	162.159.38.51^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meadow.ns.cloudflare.com`
		A	172.64.34.51^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meadow.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.74.238, 172.67.164.163
		IPv6 hints	2606:4700:3031::6815:4aee, 2606:4700:3034::ac43:a4a3
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=205, name=cloudflare-ech.com
SOA	`jimmy.ns.cloudflare.com`dns@cloudflare.com serial=2399662690

`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=1778828481

⚠️ On DNS blocklist: tif

Same first word

track-map-device.com

DNS History

6 records (6 active, 0 former)

●NSjimmy.ns.cloudflare.com2026-05-13 → 2026-05-15 · 2 obs

● 2026-05-13 21:19:48
● 2026-05-15 07:27:48

●NSmeadow.ns.cloudflare.com2026-05-13 → 2026-05-15 · 2 obs

● 2026-05-13 21:19:48
● 2026-05-15 07:27:48

●A104.21.74.2382026-05-13 → 2026-05-15 · 2 obs

● 2026-05-13 21:19:48
● 2026-05-15 07:27:48

●A172.67.164.1632026-05-13 → 2026-05-15 · 2 obs

● 2026-05-13 21:19:48
● 2026-05-15 07:27:48

●A2606:4700:3031::6815:4aee2026-05-13 → 2026-05-15 · 2 obs

● 2026-05-13 21:19:48
● 2026-05-15 07:27:48

●A2606:4700:3034::ac43:a4a32026-05-13 → 2026-05-15 · 2 obs

● 2026-05-13 21:19:48
● 2026-05-15 07:27:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net...	-
track-map-device.com	meadow.ns.cloudflare.com, jimmy.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.51

NS records: meadow.ns.cloudflare.com, jimmy.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for track-map-device.com (unsigned zone)

⏱️ Timing

Total: 172ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.164.163, 104.21.74.238`
AAAA	2	`2606:4700:3034::ac43:a4a3, 2606:4700:3031::6815:4aee`
NS	2	`jimmy.ns.cloudflare.com, meadow.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`jimmy.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

track-map-device.com points to four IP numbers: 2606:4700:3031::6815:4aee, 2606:4700:3034::ac43:a4a3, 104.21.74.238 and 172.67.164.163.

Other host names, for instance lcfbvw.click, jsgzw.net, quantaviont.xyz, afghanchaman.com and fcrukh.com share IP numbers with track-map-device.com.

Name Servers

track-map-device.com is delegated to two name servers: jimmy.ns.cloudflare.com and meadow.ns.cloudflare.com.

track-map-device.com uses the same name server setup as other domains, for instance bwpkr.info, jsbghkgh.info, support-us.app, star-transmission.com and loveplus.vn.

track-map-device.com shares name servers with other domains at least partially, for instance destinationdijon.com, xsmrm.com, saqel.top, zono.co and playjuicy.com.

these name servers are often used with arvind.ns.cloudflare.com, bella.ns.cloudflare.com and julissa.ns.cloudflare.com.

Host names with six IP numbers: jimmy.ns.cloudflare.com points to 2606:4700:58::a29f:2c4c, 2803:f800:50::6ca2:c34c, 2a06:98c1:50::ac40:234c, 108.162.195.76, 162.159.44.76 and 172.64.35.76; meadow.ns.cloudflare.com points to 2606:4700:50::a29f:2633, 2803:f800:50::6ca2:c233, 2a06:98c1:50::ac40:2233, 108.162.194.51, 162.159.38.51 and 172.64.34.51.

track-map-device.com - robtex.com