abulow.dk

📜 Historical scan 2026-08-21 20:43:31 · ← Latest scan

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

abulow.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 3 October 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 147ms

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#

324ms

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 20:52:46

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

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

147ms

113ms

110ms

AAAA

132ms

TXT

327ms

CAA

108ms

HTTPS

128ms

TLSA

39ms

SOA

67ms

MTA-STS

82ms

DNSSEC

324ms

SRV

117ms

Total

1311ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-24 03:05:45	1891ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 08:20:00	10381ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:01:11	10342ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:44:03	1830ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:43:31 shown	1311ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:32:51	6751ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 19:21:19	57408ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 19:17:15	3044ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 05:09:47	3956ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 04:59:13	2920ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 08:34:58	2931ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 11:59:40	792ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 04:39:37	2618ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 16:32:46	978ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:19:15	1581ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 01:39:32	32754ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:35:53	10044ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 20:25:56	1364ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:00:49	965ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 19:25:11	1000ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:18:43	942ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:31:00	1513ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:19:35	906ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 10:11:30	1063ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 03:03:23	1265ms	2 NS 0 A 0 MX	❓ Unknown