🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`drivermem.dev`

DNSSEC	⚠️ Not signed
A	64.29.17.65^{🇺🇸 Amazon64.29.17.0/24 EC2 Prefix}
A	216.198.79.1^{🇺🇸 Amazon216.198.79.0/24 EC2 Prefix}
NS	`ns1.vercel-dns.com` ⭐
		A	2620:4d:4000:6259:7:13:0:1^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns1.p13.nsone.net`
		A	198.51.44.13^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns1.p13.nsone.net`
NS	`ns2.vercel-dns.com`
		A	2a00:edc0:6259:7:13::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p13.nsone.net`
		A	198.51.45.13^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns2.p13.nsone.net`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1785089767

`dev`

	DNSSEC	⚠️ Not signed
	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=1

🔒 HSTS Preload (+subdomains)

Same first word

drivermem.dev

Previous names

Next names

DNS History

6 records (4 active, 2 former)

●NSns1.vercel-dns.com2026-09-27 → 2026-11-13 · 2 obs

● 2026-09-27 06:01:10
● 2026-11-13 20:55:02

●NSns2.vercel-dns.com2026-09-27 → 2026-11-13 · 2 obs

● 2026-09-27 06:01:10
● 2026-11-13 20:55:02

●A216.198.79.12026-10-21 → 2026-11-13 · 3 obs

○ 2026-09-27 06:01:10
● 2026-10-21 10:24:52
● 2026-11-13 20:55:02

○A216.198.79.652026-09-27 → 2026-09-27 · 3 obs

● 2026-09-27 06:01:10
○ 2026-10-21 10:24:52
○ 2026-11-13 20:55:02

○A64.29.17.12026-10-21 → 2026-10-21 · 4 obs

○ 2026-09-27 06:01:10
● 2026-10-21 10:24:52
○ 2026-11-13 20:29:46
○ 2026-11-13 20:55:02

●A64.29.17.652026-09-27 → 2026-11-13 · 4 obs

● 2026-09-27 06:01:10
○ 2026-10-21 10:24:52
● 2026-11-13 20:29:46
● 2026-11-13 20:55:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	10 records
drivermem.dev	ns1.vercel-dns.com, ns2.vercel-dns.com	-

✅ Authoritative Response

Server:198.51.45.13

NS records: ns1.vercel-dns.com, ns2.vercel-dns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for drivermem.dev (unsigned zone)

⏱️ Timing

Total: 594ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`64.29.17.1, 64.29.17.65`
NS	2	`ns1.vercel-dns.com, ns2.vercel-dns.com`
SOA	1	`ns1.vercel-dns.com hostmaster.nsone.net`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)

Analysis

IP Addresses

drivermem.dev directs to two IP numbers, 64.29.17.65 and 216.198.79.1

rehabvr.com.au, swellsend.app, gosubsidy.com and two other host names share IP numbers with drivermem.dev.

Name Servers

drivermem.dev uses two name servers for its delegation: ns1.vercel-dns.com and ns2.vercel-dns.com.

drivermem.dev uses the same name servers as several other domains — among them qnxfym.info, illunwo.org, bilune.ar and two more.

drivermem.dev partially shares its name servers with domains like megana.co.id and smartsoftwaresolutions.com.br.

The two host names ns1.vercel-dns.com and ns2.vercel-dns.com each have a pair of IP addresses: ns1.vercel-dns.com has 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1, and ns2.vercel-dns.com has 198.51.45.13 and 2a00:edc0:6259:7:13::2.

drivermem.dev - robtex.com

drivermem.dev

dev