agerup.dk

📜 Historical scan 2026-08-16 04:01:53 · ← Latest scan

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

agerup.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 November 1999 (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 181ms

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#

243ms

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-19 03:50:46

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	1999-11-04
Expires	2026-12-31 (65d)

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

181ms

151ms

182ms

AAAA

152ms

TXT

614ms

CAA

188ms

HTTPS

143ms

TLSA

123ms

SOA

61ms

MTA-STS

184ms

DNSSEC

243ms

SRV

219ms

Total

1552ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 15:23:56	2216ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 10:51:32	2764ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-16 01:47:41	945ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-31 23:04:18	1075ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 16:12:11	1047ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 10:58:13	10039ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 10:38:00	2892ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:29:50	1473ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:00:03	9277ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:43:50	31182ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:33:31	1671ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 19:08:22	6622ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 19:06:54	4854ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 05:13:14	10133ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 04:01:53 shown	1552ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 16:20:04	9010ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 15:45:30	841ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 07:17:36	1653ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 03:00:49	1519ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 23:42:12	4043ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 12:32:48	2443ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 08:52:39	1182ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 08:45:53	850ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 08:12:38	27150ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:19:17	31181ms	2 NS 0 A 0 MX	❓ Unknown