`device-findmy.services`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:269e^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::ac43:a829^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.38.158^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.168.41^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`kira.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:26c5^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kira.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2c5^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kira.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22c5^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kira.ns.cloudflare.com`
		A	108.162.194.197^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kira.ns.cloudflare.com`
		A	162.159.38.197^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kira.ns.cloudflare.com`
		A	172.64.34.197^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kira.ns.cloudflare.com`
NS	`trey.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bf2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1f2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`trey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21f2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`trey.ns.cloudflare.com`
		A	108.162.193.242^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
		A	172.64.33.242^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
		A	173.245.59.242^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.38.158, 172.67.168.41
		IPv6 hints	2606:4700:3032::6815:269e, 2606:4700:3034::ac43:a829
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=204, name=cloudflare-ech.com
SOA	`kira.ns.cloudflare.com`dns@cloudflare.com serial=2403796694

`services`

	DNSSEC	🔒 Signed (DS record present)
	NS	`v0n0.nic.services` ⭐
	NS	`v0n1.nic.services`
	NS	`v0n2.nic.services`
	NS	`v0n3.nic.services`
	NS	`v2n0.nic.services`
	NS	`v2n1.nic.services`
	SOA	`v0n0.nic.services`hostmaster@donuts.email serial=1778663624

⚠️ On DNS blocklist: tif

Same first word

device-findmy.us

device-findmy.services

Similar names

mydevice-find.info

findmy-device.pro

findmy-device.help

findmy-device.click

findmy-device.app

find-mydevice.live

findmy-device.us

find-mydevice.com

findmy-device.live

DNS History

6 records (6 active, 0 former)

●NSkira.ns.cloudflare.com2026-05-07 → 2026-05-13 · 2 obs

● 2026-05-07 01:06:00
● 2026-05-13 09:35:22

●NStrey.ns.cloudflare.com2026-05-07 → 2026-05-13 · 2 obs

● 2026-05-07 01:06:00
● 2026-05-13 09:35:22

●A104.21.38.1582026-05-07 → 2026-05-13 · 2 obs

● 2026-05-07 01:06:00
● 2026-05-13 09:35:22

●A172.67.168.412026-05-07 → 2026-05-13 · 2 obs

● 2026-05-07 01:06:00
● 2026-05-13 09:35:22

●A2606:4700:3032::6815:269e2026-05-07 → 2026-05-13 · 2 obs

● 2026-05-07 01:06:00
● 2026-05-13 09:35:22

●A2606:4700:3034::ac43:a8292026-05-07 → 2026-05-13 · 2 obs

● 2026-05-07 01:06:00
● 2026-05-13 09:35:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
services	v0n0.nic.services, v0n1.nic.services, v0n2.nic.services, v0n3.nic.services...	12 records
device-findmy.services	kira.ns.cloudflare.com, trey.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.242

NS records: kira.ns.cloudflare.com, trey.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for device-findmy.services (unsigned zone)

⏱️ Timing

Total: 963ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.38.158, 172.67.168.41`
AAAA	2	`2606:4700:3034::ac43:a829, 2606:4700:3032::6815:269e`
NS	2	`kira.ns.cloudflare.com, trey.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`kira.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n0.nic.services, v0n0.nic.services, v0n1.nic.services...)

Analysis

IP Addresses

device-findmy.services resolves to four IP numbers: 2606:4700:3032::6815:269e, 2606:4700:3034::ac43:a829, 104.21.38.158 and 172.67.168.41.

other host names for instance www.thenovelthief.com, vimtoday.com, chaseandassoc.com, ly-bj.com and vyos.net share IP numbers with device-findmy.services.

Name Servers

device-findmy.services is delegated to two name servers: kira.ns.cloudflare.com and trey.ns.cloudflare.com.

device-findmy.services shares the same name server setup as other domains, for example manstar.pl, fior.com.pl, apple-maps.services, aamb.us and euro-chem.org.

device-findmy.services at least partially shares name servers with other domains, for instance musictoday.com, myelariqent.com, ds-pushkino.ru, pagtour.net and inarisushi.ru.

These name servers are commonly used with rohin.ns.cloudflare.com, clint.ns.cloudflare.com and jaziel.ns.cloudflare.com.

Host names with six IP numbers:

kira.ns.cloudflare.com points to: 2606:4700:50::a29f:26c5, 2803:f800:50::6ca2:c2c5, 2a06:98c1:50::ac40:22c5, 108.162.194.197, 162.159.38.197 and 172.64.34.197; trey.ns.cloudflare.com points to: 2606:4700:58::adf5:3bf2, 2803:f800:50::6ca2:c1f2, 2a06:98c1:50::ac40:21f2, 108.162.193.242, 172.64.33.242 and 173.245.59.242.

device-findmy.services - robtex.com