clockonline.dk

📜 Historical scan 2026-08-18 22:05:11 · ← Latest scan

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

clockonline.dk is a registered .dk domain whose nameservers (ns1.masterdns.nl, ns2.masterdns.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 29 December 2017 (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 176ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.masterdns.nl	185.168.85.11 2a0a:9fc0:1053::11	ns1.masterdns.nl ns1.masterdns.nl	AS31673 Uniserver Internet B.V. AS31673 Uniserver Internet B.V.
ns2.masterdns.nl	185.168.85.12 2a0a:9fc0:1053::12	ns2.masterdns.nl ns2.masterdns.nl	AS31673 Uniserver Internet B.V. AS31673 Uniserver Internet B.V.

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

872ms

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-13 15:10:38

Field	Value
Registrar	Key-Systems GmbH
Registered	2017-12-29
Expires	2026-12-31 (74d)

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

176ms

134ms

139ms

AAAA

118ms

TXT

956ms

CAA

112ms

HTTPS

189ms

TLSA

198ms

SOA

85ms

MTA-STS

603ms

DNSSEC

872ms

SRV

932ms

Total

5369ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 22:23:52	2947ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-01 01:43:02	2890ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 01:29:38	4919ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:37:37	6925ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:23:58	11347ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:13:59	2459ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:18:02	1872ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:05:11 shown	5369ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 13:39:31	5741ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:03:42	11396ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:53:48	3217ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 04:47:55	11350ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 15:40:26	4921ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 23:26:06	3169ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:55:19	11637ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 01:02:17	2640ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 10:13:32	11310ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:06:55	10902ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 20:38:27	4039ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:10:07	3063ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 19:57:25	18679ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:31:33	9835ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:34:34	17612ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:41:55	3421ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 01:35:31	2924ms	2 NS 0 A 0 MX	❓ Unknown