2dog3d.dk

📜 Historical scan 2026-07-17 19:20:47 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

2dog3d.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 May 2004 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 54ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

🌍 A Records#

🌍

No A records found

📧 MX Records#

📧

No MX records found

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

📝

No TXT records found

✉️ SPF#

✗ No SPF record — mail spoofing not restricted

📨 DMARC#

✗ No DMARC record — mail spoofing not restricted

📬 MTA-STS#

✗ No MTA-STS policy — SMTP TLS not enforced

📈 TLSRPT#

✗ No TLSRPT record — no SMTP TLS failure reporting

📜 CAA Records#

✗ No CAA records — any CA may issue certificates

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

130ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-20 02:31:33

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-05-05
Expires	2027-05-31 (220d)

🔗 Same registrant#

0 domains

Other .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).

No other domain with this registrant in our WHOIS data yet

📋 WHOIS#

⏱️ Lookup Timing#

54ms

53ms

45ms

AAAA

45ms

TXT

316ms

CAA

46ms

HTTPS

38ms

TLSA

37ms

SOA

31ms

MTA-STS

97ms

DNSSEC

130ms

SRV

155ms

Total

821ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 17:44:44	2776ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 06:23:10	4187ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 02:49:14	5915ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 02:38:23	2329ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:37:13	29190ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:17:23	5486ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:58:23	6265ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 18:25:12	844ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 20:04:37	3958ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 16:34:52	2947ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:56:30	8951ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 00:08:49	2606ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 01:52:59	14302ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:17:31	8898ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:00:04	3923ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:45:54	1011ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:23:12	8843ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:24:59	692ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 01:13:19	760ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:28:23	769ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 03:57:05	1421ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 19:20:47 shown	821ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 18:46:35	865ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-14 20:10:18	835ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-10 22:09:57	795ms	2 NS 0 A 0 MX	❓ Unknown