advokathooge.dk

Records from scan: 2026-09-24 21:15:13 · 1268ms total · last checked 2026-10-25 22:42 (unchanged)

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

advokathooge.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 17 December 2014 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 167ms

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#

224ms

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-17 10:58:38

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-12-17
Expires	2026-12-31 (66d)

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

167ms

177ms

AAAA

179ms

TXT

600ms

CAA

134ms

HTTPS

187ms

TLSA

117ms

SOA

63ms

MTA-STS

136ms

DNSSEC

224ms

SRV

188ms

Total

1268ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-24 21:15:13 shown	1268ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 12:26:07	820ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:34:05	4741ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:27:01	1293ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:12:19	1263ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:53:12	4298ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:57:14	913ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 16:36:40	2707ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:30:33	10364ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:50:59	3273ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 01:32:09	27381ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:44:39	1150ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:16:34	10105ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 21:31:45	839ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 12:56:44	2459ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 04:44:25	10075ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:57:50	1017ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:37:25	1397ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:28:10	27172ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:01:19	32752ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:34:14	875ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:31:42	1368ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:54:06	1056ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 05:51:18	1199ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 04:57:27	10090ms	2 NS 0 A 0 MX	❓ Unknown