matildenyeland.dk

Records from scan: 2026-09-30 12:19:50  ·  1587ms total  ·  last checked 2026-11-16 09:05 (unchanged)
Lame delegation Zone File Timeline & History Scan Now

matildenyeland.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 1 September 2013 (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   305ms

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#

312ms
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-01 02:04:15
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2013-09-01
Expires2027-09-30 (317d)

Same registrant#

1 domain

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
vetur.dkPunktum dk A/S (direct)
📋 WHOIS#

Lookup Timing#

NS
305ms
A
309ms
MX
315ms
AAAA
299ms
TXT
776ms
CAA
306ms
HTTPS
276ms
TLSA
117ms
SOA
30ms
MTA-STS
132ms
DNSSEC
312ms
SRV
362ms
Total
1587ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-30 12:19:50 shown 1587ms 2 NS 0 A 0 MX Bogus
2026-09-23 18:04:43 26961ms 2 NS 0 A 0 MX Unknown
2026-08-28 04:52:58 2866ms 2 NS 0 A 0 MX Bogus
2026-08-23 07:54:44 5760ms 2 NS 0 A 0 MX Bogus
2026-08-22 07:42:03 27362ms 2 NS 0 A 0 MX Unknown
2026-08-21 07:32:40 19172ms 2 NS 0 A 0 MX Unknown
2026-08-20 06:46:45 16923ms 2 NS 0 A 0 MX Bogus
2026-08-19 06:09:32 2837ms 2 NS 0 A 0 MX Bogus
2026-08-18 03:12:56 3876ms 2 NS 0 A 0 MX Bogus
2026-08-17 02:47:22 1045ms 2 NS 0 A 0 MX Bogus
2026-08-14 13:27:17 1024ms 2 NS 0 A 0 MX Bogus
2026-08-13 12:16:37 31212ms 2 NS 0 A 0 MX Unknown
2026-08-11 15:12:35 1526ms 2 NS 0 A 0 MX Bogus
2026-08-10 10:14:55 1014ms 2 NS 0 A 0 MX Bogus
2026-08-07 16:48:12 935ms 2 NS 0 A 0 MX Bogus
2026-07-31 01:40:02 1489ms 2 NS 0 A 0 MX Bogus
2026-07-27 23:30:57 8876ms 2 NS 0 A 0 MX Bogus
2026-07-26 22:48:26 907ms 2 NS 0 A 0 MX Bogus
2026-07-25 22:09:15 998ms 2 NS 0 A 0 MX Bogus
2026-07-24 22:02:38 9710ms 2 NS 0 A 0 MX Bogus
2026-07-23 17:46:42 1073ms 2 NS 0 A 0 MX Bogus
2026-07-22 05:26:36 29156ms 2 NS 0 A 0 MX Unknown
2026-07-20 11:45:46 680ms 2 NS 0 A 0 MX Bogus
2026-07-19 01:08:59 16628ms 2 NS 0 A 0 MX Bogus
2026-07-17 23:56:27 10035ms 2 NS 0 A 0 MX Bogus