adventure-track.dk

📜 Historical scan 2026-07-26 18:52:48 · ← Latest scan

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

adventure-track.dk is a registered .dk domain whose nameservers (ns1.curanet.dk, ns2.curanet.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 January 2017 (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 291ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.curanet.dk	185.25.141.12 2a02:2339:4006:108::123	ns1.curanet.dk ns1.curanet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.curanet.dk	2a02:2339:1:10f::123:123 91.197.248.75	ns2.curanet.dk ns2.curanet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S

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

361ms

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-25 15:37:18

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-01-07
Expires	2027-01-31 (97d)

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

291ms

287ms

93ms

AAAA

98ms

TXT

570ms

CAA

88ms

HTTPS

78ms

TLSA

106ms

SOA

42ms

MTA-STS

143ms

DNSSEC

361ms

SRV

8071ms

Total

16718ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-24 19:13:36	1022ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 15:28:07	9897ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 06:19:29	2796ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 15:15:48	2734ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 02:31:45	10197ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:48:28	2525ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:47:27	5962ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:42:24	4186ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:14:08	10029ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:22:13	3344ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 02:45:46	4441ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 21:58:40	2556ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 18:34:39	1040ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 21:39:44	3671ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:22:34	4593ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 20:42:00	9993ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 00:01:42	1056ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:12:06	16949ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:52:48 shown	16718ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:32:08	9376ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:21:26	1242ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:56:37	1028ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:57:20	17837ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 15:22:04	2602ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 12:53:56	1162ms	2 NS 0 A 0 MX	❓ Unknown