clearlink.dk
Records from scan: 2026-10-16 19:15:26 · 1204ms total · last checked 2026-11-17 08:18 (unchanged)
clearlink.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 2 October 2000 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.
Nameservers#
2 records 175msA 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
Web & zone#
checked 2026-10-08 20:46:11| www | NXDOMAIN |
| www vs bare domain | Neither resolves clearlink.dk: no address www.clearlink.dk: no address |
| Wildcard | No |
| Denial of existence | NSEC3 · 0 iterations · no salt RFC 9276 ✓ |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
TLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
190ms| Check | Result |
|---|---|
| Validation Status | Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all. |
| AD Flag (resolver validates) | Not set |
| DS Record | Found |
| DNSKEY Record | Not found |
| Flags | resolution failed: failure |
SOA#
No SOA record found
Registration#
WHOIS fetched 2026-10-28 10:06:12| Field | Value |
|---|---|
| Registrar | Punktum dk A/S (direct) |
| Registered | 2000-10-02 |
| Expires | 2026-12-31 (42d) |
Same registrant#
0 domainsOther .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#
NS
A
MX
AAAA
TXT
CAA
HTTPS
TLSA
SOA
MTA-STS
DNSSEC
SRV
Total
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-10-16 19:15:26 shown | 1204ms | 2 NS 0 A 0 MX | Bogus |
| 2026-10-03 18:16:21 | 497ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-30 18:08:10 | 375ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-25 04:43:23 | 389ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-16 20:24:43 | 595ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-07 18:37:41 | 1095ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-27 11:18:18 | 1182ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-26 22:10:18 | 842ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-24 15:25:12 | 997ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-22 09:31:53 | 1113ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-05 07:09:35 | 1931ms | 2 NS 1 A 4 MX | Secure |
| 2026-07-01 21:01:45 | 677ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-26 17:04:41 | 633ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-26 01:08:16 | 597ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-19 09:34:11 | 897ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-16 21:16:25 | 718ms | 2 NS 1 A 4 MX | Secure |