aggerbyg.dk

📜 Historical scan 2026-07-08 16:53:21 · ← Latest scan

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

aggerbyg.dk is a registered .dk domain whose nameservers (ns1.danaweb.org, ns2.danaweb.org, ns3.danaweb.org and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 October 2020 (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 164ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.danaweb.org	185.25.141.12	ns1.curanet.dk	AS48854 team.blue Denmark A/S
ns2.danaweb.org	91.197.248.75	ns2.curanet.dk	AS48854 team.blue Denmark A/S
ns3.danaweb.org	185.25.141.12	ns1.curanet.dk	AS48854 team.blue Denmark A/S
ns4.danaweb.org	91.197.248.75	ns2.curanet.dk	AS48854 team.blue Denmark 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#

308ms

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-27 06:18:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2020-10-06
Expires	2026-10-31 (4d)

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

164ms

290ms

53ms

AAAA

251ms

TXT

394ms

CAA

63ms

HTTPS

64ms

TLSA

119ms

SOA

31ms

MTA-STS

106ms

DNSSEC

308ms

SRV

205ms

Total

1047ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 22:44:20	864ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-28 01:11:53	3107ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:07:15	3515ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:47:23	3098ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:36:47	6609ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:34:26	1536ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 14:58:32	1728ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 14:52:21	3975ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 20:50:47	4079ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:47:13	5189ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 15:42:40	1163ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 09:43:37	1129ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-07 19:12:30	1496ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-05 09:53:40	3108ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-28 19:07:40	10104ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:14:53	1107ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:32:49	9994ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:16:54	10021ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:44:13	1134ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:55:36	1261ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 10:57:56	1497ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:21:37	1220ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:23:00	1226ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-19 01:20:46	1438ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-18 01:02:46	1398ms	4 NS 0 A 0 MX	❓ Unknown