miltonmegatherm.dk

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

miltonmegatherm.dk is a registered .dk domain whose nameservers (ns1.aveo.dk, ns2.aveo.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 1 May 2012 (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   59ms

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#

85ms
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-10-31 00:58:53
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2012-05-01
Expires2027-05-31 (193d)

Same registrant#

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

Lookup Timing#

NS
59ms
A
60ms
MX
59ms
AAAA
59ms
TXT
294ms
CAA
59ms
HTTPS
59ms
TLSA
61ms
SOA
24ms
MTA-STS
68ms
DNSSEC
85ms
SRV
62ms
Total
1056ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-31 16:07:48 1066ms 2 NS 0 A 0 MX Bogus
2026-10-29 12:54:27 971ms 2 NS 0 A 0 MX Bogus
2026-10-07 20:19:51 872ms 2 NS 0 A 0 MX Bogus
2026-09-11 00:03:50 1209ms 2 NS 0 A 0 MX Bogus
2026-08-23 08:25:56 1582ms 2 NS 0 A 0 MX Bogus
2026-08-22 08:11:54 10009ms 2 NS 0 A 0 MX Bogus
2026-08-21 07:46:27 1620ms 2 NS 0 A 0 MX Bogus
2026-08-20 05:16:40 6540ms 2 NS 0 A 0 MX Bogus
2026-08-19 01:25:21 2662ms 2 NS 0 A 0 MX Bogus
2026-08-17 21:48:15 1623ms 2 NS 0 A 0 MX Bogus
2026-08-15 18:09:34 2866ms 2 NS 0 A 0 MX Bogus
2026-08-14 00:58:22 1280ms 2 NS 0 A 0 MX Bogus
2026-08-12 17:55:41 1446ms 2 NS 0 A 0 MX Bogus
2026-08-11 16:50:26 3005ms 2 NS 0 A 0 MX Bogus
2026-08-09 16:38:42 10073ms 2 NS 0 A 0 MX Bogus
2026-08-08 04:25:45 9978ms 2 NS 0 A 0 MX Bogus
2026-08-02 05:03:58 2799ms 2 NS 0 A 0 MX Bogus
2026-07-31 03:16:38 1117ms 2 NS 0 A 0 MX Bogus
2026-07-28 00:10:03 1383ms 2 NS 0 A 0 MX Bogus
2026-07-26 23:38:44 1204ms 2 NS 0 A 0 MX Bogus
2026-07-25 22:54:49 9013ms 2 NS 0 A 0 MX Bogus
2026-07-24 22:19:19 9989ms 2 NS 0 A 0 MX Bogus
2026-07-23 20:13:05 2339ms 2 NS 0 A 0 MX Bogus
2026-07-22 19:49:59 1281ms 2 NS 0 A 0 MX Bogus
2026-07-21 18:50:33 1119ms 2 NS 0 A 0 MX Bogus