🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`for-verify.dashdark.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐ ⚠️ Not in parent delegation
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`ns1.afternic.com` ⚠️ Not in parent delegation
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net serial=1

`dashdark.com`

	DNSSEC	⚠️ Not signed
	A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
	A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
	NS	`ns2.afternic.com` ⭐
	NS	`ns1.afternic.com`
	TXT	`v=spf1 -all`
	SOA	`ns2.afternic.com`dns@jomax.net serial=1

DNS History

5 records (4 active, 1 former)

●NSns1.afternic.com2026-03-31 → 2026-08-17 · 2 obs

● 2026-03-31 17:04:38
● 2026-08-17 04:14:50

●NSns2.afternic.com2026-03-31 → 2026-08-17 · 2 obs

● 2026-03-31 17:04:38
● 2026-08-17 04:14:50

●A13.248.169.482026-03-31 → 2026-08-17 · 2 obs

● 2026-03-31 17:04:38
● 2026-08-17 04:14:50

●A76.223.54.1462026-03-31 → 2026-08-17 · 2 obs

● 2026-03-31 17:04:38
● 2026-08-17 04:14:50

○CNAMEdashdark.com2017-08-10 → 2026-02-16 · 4 obs

● 2017-08-10 23:42:46
● 2026-02-16 06:54:06
○ 2026-03-31 17:04:38
○ 2026-08-17 04:14:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net, a.gtld-servers.net...	-
dashdark.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:173.201.66.69

NS records: ns1.afternic.com, ns2.afternic.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dashdark.com (unsigned zone)

⏱️ Timing

Total: 354ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns2.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

for-verify.dashdark.com resolves to the IP addresses 13.248.169.48 and 76.223.54.146

227-235-182.cable.dynamic.kbtelecom.net, 209-128-68-127.bayarea.net, rekapp.com plus two other host names have IP numbers in common with for-verify.dashdark.com.

Name Servers

Two name servers handle the delegation for for-verify.dashdark.com: ns1.afternic.com and ns2.afternic.com.

The name server configuration of for-verify.dashdark.com is shared with other domains, for instance tos.www.kredit.to, samoney.com, dowels.co.uk and two others.

for-verify.dashdark.com shares at least some of its name servers with other domains, including tejaswani.com, automationscript.com, suvmotors.com and two others.

These name servers are frequently seen alongside the name servers verification-cukmqwnkpi6booqjwnxbfw.ns101.verify.hn.

ns1.afternic.com and ns2.afternic.com both carry two IP addresses. The A records for ns1.afternic.com are 97.74.98.69 and 2603:5:2126::45; the A records for ns2.afternic.com are 173.201.66.69 and 2603:5:2226::45.

for-verify.dashdark.com - robtex.com