agger-weibel.dk

📜 Historical scan 2026-07-11 00:03:31 · ← Latest scan

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

agger-weibel.dk is a registered .dk domain whose nameservers (ns1.123hjemmeside.dk, ns2.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 July 2007 (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 11063ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns2.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.

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

16051ms

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-16 17:06:46

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-07-05
Expires	2027-07-31 (287d)

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

11063ms

8061ms

3050ms

AAAA

3037ms

TXT

43233ms

CAA

3068ms

HTTPS

3054ms

TLSA

8032ms

SOA

37ms

MTA-STS

16054ms

DNSSEC

16051ms

SRV

16058ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-24 01:28:40	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:17:37	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:08:07	59343ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 22:59:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:08:34	63570ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:42:44	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 23:15:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:52:16	58865ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 06:49:22	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 01:58:23	58863ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:09:17	61128ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 07:42:55	59182ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 08:25:34	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 07:49:54	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:51:11	61254ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:35:47	65305ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:07:18	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:02:44	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 02:10:38	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:13:14	63304ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 02:46:32	63278ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 02:07:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 00:37:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-14 12:01:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-11 00:03:31 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown