midtlast.dk

Historical scan 2026-07-05 07:51:05  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

midtlast.dk is a registered .dk domain whose nameservers (ns.scannet2.dk, ns2.scannet2.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 22 May 2001 (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   761ms

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

Web & zone#

latest probe, not this scan · checked 2026-10-20 07:49:39
www212.237.249.18 (AS48854) (address records, no CNAME)
www vs bare domainSame network
midtlast.dk: 212.237.249.18 (AS48854)
www.midtlast.dk: 212.237.249.18 (AS48854)
WildcardYes: any name under the zone resolves
Denial of existenceNSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

1574ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-10-20 08:04:26
FieldValue
RegistrarA/S SCANNET
Registered2001-05-22
Expires2027-06-30 (224d)

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#

NS
761ms
A
1001ms
MX
861ms
AAAA
559ms
TXT
1973ms
CAA
900ms
HTTPS
701ms
TLSA
1009ms
SOA
566ms
MTA-STS
471ms
DNSSEC
1574ms
SRV
971ms
Total
11525ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-20 07:49:39 932ms 2 NS 1 A 0 MX Secure
2026-10-06 01:43:55 564ms 2 NS 1 A 0 MX Insecure
2026-08-24 10:46:59 1127ms 2 NS 0 A 0 MX Unknown
2026-08-22 23:25:37 6672ms 2 NS 0 A 0 MX Unknown
2026-08-21 23:21:50 4976ms 2 NS 0 A 0 MX Unknown
2026-08-20 23:17:49 2903ms 2 NS 0 A 0 MX Unknown
2026-08-19 22:24:28 5649ms 2 NS 0 A 0 MX Unknown
2026-08-18 22:07:49 4944ms 2 NS 0 A 0 MX Unknown
2026-08-17 17:19:48 1111ms 2 NS 0 A 0 MX Unknown
2026-08-16 15:13:21 1059ms 2 NS 0 A 0 MX Unknown
2026-08-15 09:40:19 3776ms 2 NS 0 A 0 MX Unknown
2026-08-11 21:26:52 2806ms 2 NS 0 A 0 MX Unknown
2026-08-10 15:53:57 3783ms 2 NS 0 A 0 MX Unknown
2026-08-08 01:30:20 1197ms 2 NS 0 A 0 MX Unknown
2026-08-02 04:54:04 1178ms 2 NS 0 A 0 MX Unknown
2026-07-31 01:00:12 1239ms 2 NS 0 A 0 MX Unknown
2026-07-27 21:00:36 1114ms 2 NS 0 A 0 MX Unknown
2026-07-26 20:44:05 1109ms 2 NS 0 A 0 MX Unknown
2026-07-25 20:42:50 2596ms 2 NS 0 A 0 MX Unknown
2026-07-24 20:37:47 9871ms 2 NS 0 A 0 MX Unknown
2026-07-23 17:37:34 8948ms 2 NS 0 A 0 MX Unknown
2026-07-22 16:51:52 1191ms 2 NS 0 A 0 MX Unknown
2026-07-21 15:54:26 1184ms 2 NS 0 A 0 MX Unknown
2026-07-20 14:37:31 2785ms 2 NS 0 A 0 MX Unknown
2026-07-19 11:35:52 2410ms 2 NS 0 A 0 MX Unknown