3-r.dk

📜 Historical scan 2026-08-23 04:37:47 · ← Latest scan

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

3-r.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 18 October 2002 (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 104ms

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#

349ms

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-09 08:10:52

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2002-10-18
Expires	2026-12-31 (69d)

📋 WHOIS#

⏱️ Lookup Timing#

104ms

99ms

105ms

AAAA

90ms

TXT

392ms

CAA

103ms

HTTPS

75ms

TLSA

86ms

SOA

96ms

MTA-STS

146ms

DNSSEC

349ms

SRV

917ms

Total

2407ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-26 05:43:41	9952ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-06 12:39:56	1374ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 05:05:07	3133ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:37:47 shown	2407ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:23:59	43123ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:06:46	5595ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:50:46	1282ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:20:11	3261ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 07:16:45	992ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:11:53	29139ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 13:06:09	9348ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 22:40:35	27152ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:09:28	3075ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 06:23:19	1421ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 11:08:25	2995ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 20:48:33	2427ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 13:38:51	700ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 11:36:56	721ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 02:43:11	2861ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 01:14:35	10032ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:55:23	9045ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:22:55	8713ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:45:54	945ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 22:51:02	10352ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 21:43:36	1353ms	2 NS 0 A 0 MX	❓ Unknown