exploitable.dev - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`exploitable.dev`

DNSSEC	⚠️ Not signed
A	64.29.17.1^{🇺🇸 Amazon64.29.17.0/24 EC2 Prefix}
A	64.29.17.65^{🇺🇸 Amazon64.29.17.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`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	142.251.167.26^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f26.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f27.1e100.net`
		A	172.253.139.27^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
TXT	`google-site-verification=oAqqjxZwYYyBfTdnXzak7LOMCOIf33ijfopmurrOaXo`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1783090958

`dev`

	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=1

🔒 HSTS Preload (+subdomains)

Same first word

exploitable.systems

exploitable.app

exploitable.org

exploitable.co

exploitable.com

exploitable.ai

exploitable.xyz

exploitable.dev

Previous names

Next names

DNS History

7 records (5 active, 2 former)

●NSns1.vercel-dns.com2026-08-17 → 2026-09-01 · 2 obs

● 2026-08-17 19:00:40
● 2026-09-01 15:52:24

●NSns2.vercel-dns.com2026-08-17 → 2026-09-01 · 2 obs

● 2026-08-17 19:00:40
● 2026-09-01 15:52:24

●MXsmtp.google.com2026-08-17 → 2026-09-01 · 2 obs

● 2026-08-17 19:00:40
● 2026-09-01 15:52:24

○A216.198.79.12026-08-20 → 2026-08-30 · 14 obs

○ 2026-08-17 19:00:40
● 2026-08-20 20:35:16
○ 2026-08-21 13:39:14
● 2026-08-21 15:04:20
○ 2026-08-22 20:26:22
● 2026-08-22 23:24:06
○ 2026-08-23 13:50:54
● 2026-08-25 06:12:32
○ 2026-08-28 10:12:58
● 2026-08-29 22:32:32
○ 2026-08-30 04:20:26
● 2026-08-30 22:24:14
○ 2026-09-01 01:13:46
○ 2026-09-01 15:52:24

○A216.198.79.652026-08-20 → 2026-08-31 · 12 obs

○ 2026-08-17 19:00:40
● 2026-08-20 20:35:16
○ 2026-08-21 15:04:20
● 2026-08-22 20:26:22
○ 2026-08-23 00:51:50
● 2026-08-23 13:50:54
○ 2026-08-24 15:45:24
● 2026-08-28 10:12:58
○ 2026-08-30 10:42:52
● 2026-08-31 16:11:34
○ 2026-09-01 09:27:24
○ 2026-09-01 15:52:24

●A64.29.17.12026-08-17 → 2026-09-01 · 18 obs

● 2026-08-17 19:00:40
○ 2026-08-20 20:35:16
● 2026-08-21 13:39:14
○ 2026-08-21 15:04:20
● 2026-08-23 00:51:50
○ 2026-08-23 22:07:06
● 2026-08-24 15:45:24
○ 2026-08-25 06:12:32
● 2026-08-25 07:52:30
○ 2026-08-28 10:12:58
● 2026-08-29 20:27:46
○ 2026-08-29 22:32:32
● 2026-08-30 04:20:26
○ 2026-08-31 16:11:34
● 2026-09-01 01:13:46
○ 2026-09-01 03:19:40
● 2026-09-01 09:27:24
● 2026-09-01 15:52:24

●A64.29.17.652026-08-17 → 2026-09-01 · 12 obs

● 2026-08-17 19:00:40
○ 2026-08-20 20:35:16
● 2026-08-21 15:04:20
○ 2026-08-22 23:24:06
● 2026-08-23 22:07:06
○ 2026-08-25 07:52:30
● 2026-08-28 10:12:58
○ 2026-08-29 20:27:46
● 2026-08-30 10:42:52
○ 2026-08-30 22:24:14
● 2026-09-01 03:19:40
● 2026-09-01 15:52:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
exploitable.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 exploitable.dev (unsigned zone)

⏱️ Timing

Total: 688ms | 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`
MX	1	`smtp.google.com (pri: 1)`
TXT	1	`google-site-verification=oAqqjxZwYYyBfTd`
SOA	1	`ns1.vercel-dns.com hostmaster.nsone.net`

Analysis

IP Addresses

exploitable.dev has two IP addresses: 64.29.17.1 and 64.29.17.65

Among the host names that share IP numbers with exploitable.dev are mxnpro.ovh, alann.site, dispatch.autos and two others.

Name Servers

exploitable.dev is delegated to two name servers: ns1.vercel-dns.com and ns2.vercel-dns.com.

exploitable.dev has the same name server delegation as a number of other domains, such as hkabra.tech, pastoverde.us, renaspress.com and two more.

exploitable.dev has overlapping name servers with several other domains — among them treggandnaomi.com, lampungcysec.my.id, mikebobiney.com and oregonunlocked.org.

ns1.vercel-dns.com and ns2.vercel-dns.com each resolve to two IP addresses: ns1.vercel-dns.com points to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1, while ns2.vercel-dns.com points to 198.51.45.13 and 2a00:edc0:6259:7:13::2.

Mail Servers

exploitable.dev routes its mail through a single mail server, smtp.google.com.

exploitable.dev has the same mail server arrangement as a number of other domains, for example meridianbiologic.com, servimax.co, aircompressorpiping.net and two more.

exploitable.dev shares at least some of its mail servers with other domains — for example drmezoistvan.hu, oisgym.no, kingcapcred.info and two more.

It is common for these mail servers to co-occur with aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and alt3.aspmx.l.google.com as mail servers.

smtp.google.com directs to 9 IP numbers, including 142.251.167.26, 142.251.167.27 and 172.253.139.27, along with 6 other.