advodanslagelse.dk

📜 Historical scan 2026-08-01 10:18:30 · ← Latest scan

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

advodanslagelse.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 4 May 2017 (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 67ms

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#

144ms

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-18 22:50:27

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-05-04
Expires	2027-05-31 (217d)

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

67ms

75ms

103ms

AAAA

94ms

TXT

324ms

CAA

82ms

HTTPS

66ms

TLSA

82ms

SOA

21ms

MTA-STS

60ms

DNSSEC

144ms

SRV

153ms

Total

921ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-02 22:53:01	1337ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-31 11:45:00	49351ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 09:33:31	1542ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:28:53	1165ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:14:42	6292ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:04:54	1832ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:17:24	11125ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:48:44	4410ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 21:46:52	10117ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 15:45:57	23204ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 02:27:49	10283ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 07:17:02	1728ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 03:57:56	969ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:49:15	877ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 08:17:06	1550ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 13:00:28	1000ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 10:18:30 shown	921ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 22:26:07	1053ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 16:26:57	1082ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:55:31	8894ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 15:08:34	8891ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:51:03	1686ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 13:57:12	984ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:35:32	854ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 02:35:55	884ms	2 NS 0 A 0 MX	❓ Unknown