lufthavnsparken.dk

Historical scan 2026-08-17 01:05:26  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

lufthavnsparken.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 May 2003 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. We saw it become registrar-handled on 5 November 2026, when it moved from direct registration at Punktum to NHL DATA ApS. 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   154ms

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-11-05 02:21:55
www185.206.180.167 185.206.180.185 2a0b:1640:1:1:1013:1:1:1 2a0b:1640:1:1:1:1:1783:3454 (AS205787) (address records, no CNAME)
www vs bare domainSame network
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

9188ms
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-11-05 02:50:46
FieldValue
RegistrarNHL DATA ApS
Registered2003-05-01
Expires2027-05-31 (193d)

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
154ms
A
2055ms
MX
146ms
AAAA
185ms
TXT
635ms
CAA
196ms
HTTPS
150ms
TLSA
116ms
SOA
28ms
MTA-STS
153ms
DNSSEC
9188ms
SRV
207ms
Total
10102ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-05 02:21:55 1065ms 4 NS 2 A 0 MX Secure
2026-11-02 04:47:41 1800ms 2 NS 0 A 0 MX Unknown
2026-10-01 01:59:49 1436ms 2 NS 0 A 0 MX Unknown
2026-09-13 11:39:30 2746ms 2 NS 0 A 0 MX Unknown
2026-08-23 14:12:12 912ms 2 NS 0 A 0 MX Unknown
2026-08-22 13:16:31 2874ms 2 NS 0 A 0 MX Unknown
2026-08-21 12:52:57 2946ms 2 NS 0 A 0 MX Unknown
2026-08-20 12:40:52 1834ms 2 NS 0 A 0 MX Unknown
2026-08-19 05:56:20 4222ms 2 NS 0 A 0 MX Unknown
2026-08-18 03:32:26 10220ms 2 NS 0 A 0 MX Unknown
2026-08-17 01:05:26 shown 10102ms 2 NS 0 A 0 MX Unknown
2026-08-14 16:04:11 10165ms 2 NS 0 A 0 MX Unknown
2026-08-13 03:35:30 2749ms 2 NS 0 A 0 MX Unknown
2026-08-11 22:58:57 3854ms 2 NS 0 A 0 MX Unknown
2026-08-10 15:30:34 10142ms 2 NS 0 A 0 MX Unknown
2026-08-08 17:48:04 1510ms 2 NS 0 A 0 MX Unknown
2026-08-03 14:28:59 44089ms 2 NS 0 A 0 MX Unknown
2026-07-31 06:05:26 962ms 2 NS 0 A 0 MX Unknown
2026-07-27 13:29:30 934ms 2 NS 0 A 0 MX Unknown
2026-07-26 12:28:34 1381ms 2 NS 0 A 0 MX Unknown
2026-07-25 11:58:26 833ms 2 NS 0 A 0 MX Unknown
2026-07-24 11:41:19 999ms 2 NS 0 A 0 MX Unknown
2026-07-23 08:23:56 1468ms 2 NS 0 A 0 MX Unknown
2026-07-22 05:06:34 8717ms 2 NS 0 A 0 MX Unknown
2026-07-20 22:00:46 10091ms 2 NS 0 A 0 MX Unknown