jordcertifikatdanmark.dk

Historical scan 2026-07-16 23:19:13  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

jordcertifikatdanmark.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 November 2023 (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   51ms

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#

113ms
CheckResult
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
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-10 21:40:24
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2023-11-02
Expires2027-11-01 (348d)

Same registrant#

2 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).

DomainRegistrar
abcmiljø.dkPunktum dk A/S (direct)
jordcertifikat.dkPunktum dk A/S (direct)
📋 WHOIS#

Lookup Timing#

NS
51ms
A
46ms
MX
47ms
AAAA
53ms
TXT
237ms
CAA
54ms
HTTPS
42ms
TLSA
29ms
SOA
31ms
MTA-STS
90ms
DNSSEC
113ms
SRV
8180ms
Total
8709ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-25 14:42:38 1265ms 2 NS 0 A 0 MX Bogus
2026-09-15 18:53:41 1435ms 2 NS 0 A 0 MX Bogus
2026-08-23 20:37:09 1526ms 2 NS 0 A 0 MX Bogus
2026-08-22 19:04:11 6360ms 2 NS 0 A 0 MX Bogus
2026-08-21 18:51:01 2957ms 2 NS 0 A 0 MX Bogus
2026-08-20 18:47:43 17374ms 2 NS 0 A 0 MX Bogus
2026-08-19 17:28:42 31176ms 2 NS 0 A 0 MX Unknown
2026-08-18 17:27:23 3978ms 2 NS 0 A 0 MX Bogus
2026-08-16 21:51:46 25907ms 2 NS 0 A 0 MX Unknown
2026-08-15 14:23:07 2917ms 2 NS 0 A 0 MX Bogus
2026-08-14 12:09:47 1357ms 2 NS 0 A 0 MX Bogus
2026-08-13 08:07:18 10125ms 2 NS 0 A 0 MX Bogus
2026-08-10 15:16:29 3654ms 2 NS 0 A 0 MX Bogus
2026-08-09 13:51:01 16881ms 2 NS 0 A 0 MX Bogus
2026-08-06 21:14:59 10012ms 2 NS 0 A 0 MX Bogus
2026-07-31 18:11:06 16789ms 2 NS 0 A 0 MX Unknown
2026-07-29 08:35:49 10057ms 2 NS 0 A 0 MX Bogus
2026-07-27 18:42:52 813ms 2 NS 0 A 0 MX Bogus
2026-07-26 17:56:41 643ms 2 NS 0 A 0 MX Bogus
2026-07-25 17:27:36 959ms 2 NS 0 A 0 MX Bogus
2026-07-24 16:18:20 16630ms 2 NS 0 A 0 MX Bogus
2026-07-23 15:50:01 722ms 2 NS 0 A 0 MX Bogus
2026-07-22 15:04:24 741ms 2 NS 0 A 0 MX Bogus
2026-07-20 22:51:52 8771ms 2 NS 0 A 0 MX Bogus
2026-07-19 08:04:47 911ms 2 NS 0 A 0 MX Bogus