`locatemydevice.app`

DNSSEC	⚠️ Not signed
NS	`melissa.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:50::adf5:3ac7^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0c7^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`melissa.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20c7^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`melissa.ns.cloudflare.com`
		A	108.162.192.199^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
		A	172.64.32.199^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
		A	173.245.58.199^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melissa.ns.cloudflare.com`
NS	`newt.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:58::adf5:3bd4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1d4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`newt.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21d4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`newt.ns.cloudflare.com`
		A	108.162.193.212^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`
		A	172.64.33.212^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`
		A	173.245.59.212^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`newt.ns.cloudflare.com`

`app`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=101427

⚠️ On DNS blocklist: tif
🔒 HSTS Preload (+subdomains)

Same first word

locatemydevice.app

locatemydevice.com

locatemydevice.info

DNS History

2 records (2 active, 0 former)

●NSmelissa.ns.cloudflare.com2026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 08:14:40
● 2026-07-29 14:18:40

●NSnewt.ns.cloudflare.com2026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 08:14:40
● 2026-07-29 14:18:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
locatemydevice.app	newt.ns.cloudflare.com, melissa.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.192.199

NS records: newt.ns.cloudflare.com, melissa.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for locatemydevice.app (unsigned zone)

⏱️ Timing

Total: 2744ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

locatemydevice.app uses two name servers for its delegation: melissa.ns.cloudflare.com and newt.ns.cloudflare.com.

The name server configuration of locatemydevice.app is shared with other domains, for instance login-fmi.app, findmyld.support, localiser-maps.services and two others.

locatemydevice.app has at least partial name server overlap with other domains, such as cmi-icm.ca, giorre.com, gotomyapartment.com and two others.

These name servers tend to appear together with the name servers earl.ns.cloudflare.com, devin.ns.cloudflare.com and ajay.ns.cloudflare.com.

Hosts with 6 IP addresses each:

Hostname melissa.ns.cloudflare.com directs to 108.162.192.199, 172.64.32.199 and 173.245.58.199 along with 3 other IP addresses.

Hostname newt.ns.cloudflare.com directs to 108.162.193.212, 172.64.33.212 and 173.245.59.212 along with 3 other IP addresses.

locatemydevice.app - robtex.com