abelgamst.dk

📜 Historical scan 2026-07-20 03:02:01 · ← Latest scan

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

abelgamst.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 June 2006 (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 75ms

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#

187ms

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-15 05:04:22

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-06-08
Expires	2027-06-30 (249d)

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

75ms

66ms

70ms

AAAA

68ms

TXT

281ms

CAA

77ms

HTTPS

69ms

TLSA

45ms

SOA

58ms

MTA-STS

132ms

DNSSEC

187ms

SRV

164ms

Total

849ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-21 16:18:16	39916ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 03:00:12	1506ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:02:52	6043ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:59:35	4342ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 22:56:10	1570ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:49:36	5284ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:51:34	4952ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 17:20:04	10139ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:19:09	1018ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 23:58:46	962ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 14:36:32	55320ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:23:48	3296ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 20:17:42	3464ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 13:18:33	3328ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 08:22:18	1480ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 17:44:54	2642ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:34:14	1491ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:22:21	18959ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:56:56	1026ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 12:44:36	934ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:09:48	1111ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 10:44:51	907ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:26:25	802ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:02:01 shown	849ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 17:52:25	1089ms	2 NS 0 A 0 MX	❓ Unknown