nordicreuse.dk

📜 Historical scan 2026-08-23 21:55:33 · ← Latest scan

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

nordicreuse.dk is a registered .dk domain whose nameservers (ns1.hostingpalvelu.fi, ns2.hostingpalvelu.fi) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 10 January 2024 (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 1252ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.hostingpalvelu.fi	31.217.192.68 31.217.192.71	ns1.hostingpalvelu.fi a71.cloudhosting.fi	AS58003 Planeetta Internet Oy AS58003 Planeetta Internet Oy
ns2.hostingpalvelu.fi	31.217.193.155 31.217.196.110	ns210.hostingpalvelu.fi ns110.hostingpalvelu.fi	AS58003 Planeetta Internet Oy AS58003 Planeetta Internet 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#

1385ms

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-26 14:54:43

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2024-01-10
Expires	2027-01-09 (73d)

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

1252ms

1290ms

1260ms

AAAA

1396ms

TXT

6398ms

CAA

1279ms

HTTPS

1269ms

TLSA

1320ms

SOA

64ms

MTA-STS

1286ms

DNSSEC

1385ms

SRV

1296ms

Total

10939ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 13:59:49	6669ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 09:00:39	13431ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 21:23:35	6931ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:55:33 shown	10939ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:04:01	4693ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:00:57	13488ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:57:28	2819ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 17:02:06	7110ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 16:54:56	13935ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:37:45	7204ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 09:17:56	8810ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 09:11:55	1640ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 04:04:36	7626ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 13:42:19	7269ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 05:41:43	14077ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 16:00:56	9447ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:08:59	9290ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:57:34	1140ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:38:04	17102ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:24:13	9259ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:52:22	1441ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:23:24	983ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:49:27	17166ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 16:19:19	1385ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 15:44:30	16951ms	2 NS 0 A 0 MX	❓ Unknown