adolphi.dk

📜 Historical scan 2026-08-21 13:11:01 · ← Latest scan

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

adolphi.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 1 June 2001 (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 87ms

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#

303ms

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-25 14:02:39

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-06-01
Expires	2027-06-30 (247d)

🔗 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#

87ms

83ms

81ms

AAAA

81ms

TXT

323ms

CAA

86ms

HTTPS

86ms

TLSA

93ms

SOA

62ms

MTA-STS

151ms

DNSSEC

303ms

SRV

159ms

Total

1221ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 09:16:41	1307ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 14:57:29	1518ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 20:21:07	1324ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-16 15:43:25	52226ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:55:53	1177ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:32:09	1274ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:11:01 shown	1221ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:45:31	10259ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:37:29	27672ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:04:44	5053ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 03:51:59	1618ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 18:55:35	10247ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 04:57:23	3607ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 08:15:07	3034ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 06:09:37	1537ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 23:07:12	2578ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 05:10:12	1484ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:29:10	804ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 01:59:44	1376ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:17:20	885ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 00:54:30	1349ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 22:57:37	901ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:47:42	1029ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 15:40:53	860ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 14:42:14	8751ms	2 NS 0 A 0 MX	❓ Unknown