finken.dk

Historical scan 2026-07-14 04:38:12  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

finken.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 20 February 2003 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. We saw it become registrar-handled on 8 November 2026, when it moved from direct registration at Punktum to ONE.COM A/S. 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   4030ms

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-08 03:21:21
www46.30.211.38 (AS51468) (address records, no CNAME)
www vs bare domainSame network
finken.dk: 46.30.211.38 (AS51468)
www.finken.dk: 46.30.211.38 (AS51468)
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#

10062ms
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: timed out

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-08 03:46:47
FieldValue
RegistrarONE.COM A/S
Registered2003-02-20
Expires2027-02-28 (99d)

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
4030ms
A
4028ms
MX
4028ms
AAAA
4028ms
TXT
16173ms
CAA
4017ms
HTTPS
4027ms
TLSA
73ms
SOA
4027ms
MTA-STS
4039ms
DNSSEC
10062ms
SRV
4031ms
Total
27202ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-08 03:21:21 385ms 2 NS 1 A 1 MX Secure
2026-11-03 01:22:02 336ms 2 NS 1 A 1 MX Secure
2026-11-02 00:06:15 745ms 2 NS 1 A 1 MX Insecure
2026-09-01 06:11:46 10047ms 2 NS 0 A 0 MX Unknown
2026-08-24 05:03:48 4463ms 2 NS 0 A 0 MX Unknown
2026-08-23 04:13:01 1538ms 2 NS 0 A 0 MX Unknown
2026-08-22 04:03:08 5470ms 2 NS 0 A 0 MX Unknown
2026-08-21 03:52:28 9316ms 2 NS 0 A 0 MX Unknown
2026-08-20 02:58:38 1345ms 2 NS 0 A 0 MX Unknown
2026-08-19 00:36:56 10114ms 2 NS 0 A 0 MX Unknown
2026-08-17 13:22:19 2909ms 2 NS 0 A 0 MX Unknown
2026-08-13 16:34:29 2769ms 2 NS 0 A 0 MX Unknown
2026-08-12 15:41:53 1455ms 2 NS 0 A 0 MX Unknown
2026-08-11 05:47:30 2502ms 2 NS 0 A 0 MX Unknown
2026-08-10 00:49:09 860ms 2 NS 0 A 0 MX Unknown
2026-08-07 21:58:29 862ms 2 NS 0 A 0 MX Unknown
2026-07-31 15:19:08 811ms 2 NS 0 A 0 MX Unknown
2026-07-27 15:37:44 920ms 2 NS 0 A 0 MX Unknown
2026-07-26 15:20:35 981ms 2 NS 0 A 0 MX Unknown
2026-07-25 15:13:03 9162ms 2 NS 0 A 0 MX Unknown
2026-07-24 14:54:26 2794ms 2 NS 0 A 0 MX Unknown
2026-07-23 13:03:46 888ms 2 NS 0 A 0 MX Unknown
2026-07-21 00:05:37 8790ms 2 NS 0 A 0 MX Unknown
2026-07-19 02:50:02 964ms 2 NS 0 A 0 MX Unknown
2026-07-18 02:01:40 993ms 2 NS 0 A 0 MX Unknown