flottemænd.dk xn--flottemnd-m3a.dk

Records from scan: 2026-10-29 09:17:37  ·  1758ms total  ·  last checked 2026-11-19 11:02 (unchanged)
Lame delegation Zone File Timeline & History Scan Now

flottemænd.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 3 May 2008 (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   196ms

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#

274ms
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-30 13:09:55
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2008-05-03
Expires2027-05-31 (192d)

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
196ms
A
194ms
MX
201ms
AAAA
195ms
TXT
973ms
CAA
200ms
HTTPS
194ms
TLSA
198ms
SOA
22ms
MTA-STS
202ms
DNSSEC
274ms
SRV
205ms
Total
1758ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-29 09:17:37 shown 1758ms 2 NS 0 A 0 MX Bogus
2026-10-21 23:38:57 65535ms 2 NS 0 A 0 MX Bogus
2026-08-24 11:30:10 1415ms 2 NS 0 A 0 MX Bogus
2026-08-23 07:09:02 3900ms 2 NS 0 A 0 MX Bogus
2026-08-22 06:55:12 10278ms 2 NS 0 A 0 MX Bogus
2026-08-21 06:41:02 13390ms 2 NS 0 A 0 MX Bogus
2026-08-20 06:02:22 1272ms 2 NS 0 A 0 MX Bogus
2026-08-19 05:17:56 1970ms 2 NS 0 A 0 MX Bogus
2026-08-18 03:51:37 2932ms 2 NS 0 A 0 MX Bogus
2026-08-14 13:09:31 3884ms 2 NS 0 A 0 MX Bogus
2026-08-13 04:03:38 4394ms 2 NS 0 A 0 MX Bogus
2026-08-10 20:57:56 3520ms 2 NS 0 A 0 MX Bogus
2026-08-09 15:43:13 3182ms 2 NS 0 A 0 MX Bogus
2026-08-08 15:33:14 16623ms 2 NS 0 A 0 MX Bogus
2026-08-06 22:59:18 10236ms 2 NS 0 A 0 MX Bogus
2026-07-31 20:46:52 8761ms 2 NS 0 A 0 MX Bogus
2026-07-30 11:25:42 1376ms 2 NS 0 A 0 MX Bogus
2026-07-29 07:45:38 2853ms 2 NS 0 A 0 MX Bogus
2026-07-27 13:44:49 1039ms 2 NS 0 A 0 MX Bogus
2026-07-26 13:04:08 10046ms 2 NS 0 A 0 MX Bogus
2026-07-25 12:31:00 945ms 2 NS 0 A 0 MX Bogus
2026-07-24 12:20:21 1285ms 2 NS 0 A 0 MX Bogus
2026-07-23 10:40:51 2954ms 2 NS 0 A 0 MX Bogus
2026-07-22 10:23:41 43061ms 2 NS 0 A 0 MX Bogus
2026-07-21 08:47:15 10124ms 2 NS 0 A 0 MX Bogus