madogvand.dk

Historical scan 2026-08-21 21:01:44  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

madogvand.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 January 2009 (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   331ms

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#

630ms
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 20:24:06
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2009-01-02
Expires2027-01-31 (72d)

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

Lookup Timing#

NS
331ms
A
388ms
MX
350ms
AAAA
371ms
TXT
1288ms
CAA
377ms
HTTPS
388ms
TLSA
194ms
SOA
239ms
MTA-STS
433ms
DNSSEC
630ms
SRV
421ms
Total
3932ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-01 03:45:49 1315ms 2 NS 0 A 0 MX Bogus
2026-09-29 22:01:26 1364ms 2 NS 0 A 0 MX Bogus
2026-09-25 13:36:54 27084ms 2 NS 0 A 0 MX Unknown
2026-08-23 22:06:40 16698ms 2 NS 0 A 0 MX Bogus
2026-08-22 21:07:38 1382ms 2 NS 0 A 0 MX Bogus
2026-08-21 21:01:44 shown 3932ms 2 NS 0 A 0 MX Bogus
2026-08-20 20:58:13 1243ms 2 NS 0 A 0 MX Bogus
2026-08-19 20:35:58 2031ms 2 NS 0 A 0 MX Bogus
2026-08-18 20:29:06 2526ms 2 NS 0 A 0 MX Bogus
2026-08-17 17:01:36 3817ms 2 NS 0 A 0 MX Bogus
2026-08-15 10:11:05 9272ms 2 NS 0 A 0 MX Bogus
2026-08-14 02:03:23 26721ms 2 NS 0 A 0 MX Unknown
2026-08-12 06:35:16 3802ms 2 NS 0 A 0 MX Bogus
2026-08-11 04:41:27 3842ms 2 NS 0 A 0 MX Bogus
2026-08-10 02:04:50 4322ms 2 NS 0 A 0 MX Bogus
2026-08-05 11:19:00 47997ms 2 NS 0 A 0 MX Unknown
2026-07-31 11:34:11 797ms 2 NS 0 A 0 MX Bogus
2026-07-27 20:39:11 31189ms 2 NS 0 A 0 MX Unknown
2026-07-26 19:14:59 845ms 2 NS 0 A 0 MX Bogus
2026-07-25 19:04:09 770ms 2 NS 0 A 0 MX Bogus
2026-07-24 18:00:38 872ms 2 NS 0 A 0 MX Bogus
2026-07-23 17:11:10 8703ms 2 NS 0 A 0 MX Bogus
2026-07-22 16:41:18 797ms 2 NS 0 A 0 MX Bogus
2026-07-21 07:40:19 958ms 2 NS 0 A 0 MX Bogus
2026-07-20 03:45:48 865ms 2 NS 0 A 0 MX Bogus