zubject.dk

📜 Historical scan 2026-07-05 14:44:44 · ← Latest scan

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

zubject.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 September 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 365ms

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#

438ms

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 21:33:09

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-09-04
Expires	2027-09-30 (345d)

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

365ms

258ms

297ms

AAAA

322ms

TXT

797ms

CAA

345ms

HTTPS

366ms

TLSA

173ms

SOA

292ms

MTA-STS

399ms

DNSSEC

438ms

SRV

387ms

Total

3283ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 07:48:32	1209ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-19 11:48:24	38965ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 05:15:37	902ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 02:51:55	1433ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 02:35:47	954ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:00:40	1660ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:45:12	5085ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:15:33	2957ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:34:20	35271ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:48:49	756ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:44:08	3221ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 12:43:26	8739ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 10:53:48	1682ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 13:04:37	1427ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 07:00:18	2460ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:40:00	1454ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:09:31	899ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:59:16	816ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:26:24	2863ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:09:22	8934ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 23:37:47	839ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 11:30:47	1409ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 05:15:14	10086ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 04:09:23	1002ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 23:16:32	27208ms	2 NS 0 A 0 MX	❓ Unknown