fidelix.dk

📜 Historical scan 2026-07-06 21:48:02 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

fidelix.dk is a registered .dk domain whose nameservers (ns.nebula.fi, ns2.nebula.fi) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 April 2018 (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 16059ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.nebula.fi	2001:1bc8:100c:a180::225 217.30.180.225	ns.nebula.fi ns.nebula.fi	AS29422 Telia Cygate Oy AS29422 Telia Cygate Oy
ns2.nebula.fi	2001:1bc8:103:9::17 217.30.182.225	ns2.nebula.fi ns2.nebula.fi	AS29422 Telia Cygate Oy AS29422 Telia Cygate Oy

🌍 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#

16084ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-28 05:35:03

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2018-04-13
Expires	2027-04-30 (184d)

🔗 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#

16059ms

16060ms

16055ms

AAAA

16062ms

TXT

27371ms

CAA

16049ms

HTTPS

1552ms

TLSA

2105ms

SOA

60ms

MTA-STS

831ms

DNSSEC

16084ms

SRV

16073ms

Total

47043ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 21:39:46	57128ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 05:50:33	57243ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 01:11:03	63749ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:26:22	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:20:52	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:12:20	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 14:54:14	55322ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 14:51:12	54324ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:42:42	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 07:54:21	61435ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 21:29:16	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 02:31:30	56968ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 14:55:31	57410ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 06:36:23	57433ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 03:10:20	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 22:01:23	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 23:39:28	63239ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 22:43:47	50423ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 21:31:19	55261ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:29:46	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 21:15:43	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:52:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 20:13:48	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:43:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 18:14:33	65535ms	2 NS 0 A 0 MX	❓ Unknown