aggerland.dk

📜 Historical scan 2026-08-11 17:29:42 · ← Latest scan

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

aggerland.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 8 March 2010 (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 338ms

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#

415ms

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:22:58

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-03-08
Expires	2027-03-31 (155d)

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

338ms

321ms

320ms

AAAA

337ms

TXT

1136ms

CAA

323ms

HTTPS

344ms

TLSA

169ms

SOA

156ms

MTA-STS

308ms

DNSSEC

415ms

SRV

384ms

Total

2730ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-26 00:12:06	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-01 03:58:29	1214ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 04:09:40	1310ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-18 23:34:09	2804ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 21:43:52	10193ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 08:40:10	1619ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 02:18:25	8947ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 02:16:09	1495ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:11:34	1263ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 01:28:36	2899ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 23:24:31	2393ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:05:13	1425ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:22:09	977ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:05:13	10190ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:55:58	2994ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 17:29:42 shown	2730ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:37:56	26331ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 01:41:03	2447ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 04:17:51	769ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 11:34:32	1406ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 05:31:00	828ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:00:17	1047ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:35:43	685ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:27:11	10138ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:13:55	33268ms	2 NS 0 A 0 MX	❓ Unknown