zaber.dk

📜 Historical scan 2026-08-15 21:12:12 · ← Latest scan

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

zaber.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 6 November 2005 (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 42ms

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#

133ms

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 04:56:53

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2005-11-06
Expires	2026-11-30 (39d)

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

42ms

36ms

65ms

AAAA

49ms

TXT

344ms

CAA

66ms

HTTPS

55ms

TLSA

90ms

SOA

24ms

MTA-STS

59ms

DNSSEC

133ms

SRV

216ms

Total

921ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 14:52:34	1812ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-03 07:32:57	27364ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:37:48	10130ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:31:22	2904ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:22:59	1071ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:07:41	1306ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:47:25	29486ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:12:42	10182ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:08:22	1103ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:12:12 shown	921ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:15:29	1061ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:47:20	4510ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 09:14:06	10127ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:47:41	29277ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 04:12:14	784ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 00:31:22	2434ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 19:08:52	10044ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:51:11	1032ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:30:46	846ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:23:52	16974ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:41:35	825ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:57:38	980ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 18:07:48	48779ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 16:21:24	8970ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 13:49:51	10098ms	2 NS 0 A 0 MX	❓ Unknown