otto-ohrt.dk

📜 Historical scan 2026-07-31 16:26:03 · ← Latest scan

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

otto-ohrt.dk is a registered .dk domain whose nameservers (ns1.servage.net, ns2.servage.net, ns3.servage.net and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 24 April 2008 (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#

4 records 16041ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.servage.net	—	—	—
ns2.servage.net	—	—	—
ns3.servage.net	—	—	—
ns4.servage.net	—	—	—

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

16076ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-20 20:44:36

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-04-24
Expires	2027-04-30 (191d)

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

16041ms

16034ms

16030ms

AAAA

16044ms

TXT

17245ms

CAA

16051ms

HTTPS

16047ms

TLSA

52ms

SOA

16044ms

MTA-STS

227ms

DNSSEC

16076ms

SRV

8080ms

Total

50319ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-24 00:29:05	4081ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:50:12	1864ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:42:07	50348ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:29:54	1551ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 16:59:19	9651ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 16:58:19	10047ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 16:23:45	4031ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-13 09:10:59	4540ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 07:06:21	1562ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:50:59	1564ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-07 11:12:13	1637ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-03 04:47:41	1507ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-31 16:26:03 shown	50319ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:55:18	33158ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:07:13	33915ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:14:54	1562ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:12:55	1493ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:07:11	1617ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 21:52:35	33410ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:02:22	38018ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-20 17:24:33	38423ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-19 16:15:16	1510ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-18 06:42:14	1467ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-17 02:33:35	33180ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-12 14:13:41	1517ms	4 NS 0 A 0 MX	❓ Unknown