solvetur.dk

📜 Historical scan 2026-08-19 22:52:43 · ← Latest scan

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

solvetur.dk is a registered .dk domain whose nameservers (ns1.misspark.com, ns2.misspark.com, ns3.misspark.com and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It 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#

4 records 836ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.misspark.com	162.159.24.173 2400:cb00:2049:1::a29f:18ad	ns1.misspark.com —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns2.misspark.com	162.159.25.99 2400:cb00:2049:1::a29f:1963	ns2.misspark.com —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns3.misspark.com	162.159.25.16 2400:cb00:2049:1::a29f:1910	ns3.misspark.com —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns4.misspark.com	162.159.24.87 2400:cb00:2049:1::a29f:1857	ns4.misspark.com —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.

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

1071ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

836ms

587ms

719ms

AAAA

809ms

TXT

2998ms

CAA

717ms

HTTPS

778ms

TLSA

464ms

SOA

324ms

MTA-STS

996ms

DNSSEC

1071ms

SRV

815ms

Total

7032ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 23:10:47	2945ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-25 21:40:27	3811ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-05 07:27:03	3861ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-01 00:31:54	11408ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-24 03:55:19	4350ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 01:08:54	3163ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 01:04:21	11443ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:58:51	2121ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:52:43 shown	7032ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:41:25	7699ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:18:35	7170ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 14:41:21	5493ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:52:22	4075ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 01:47:02	11692ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:47:46	6612ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-09 15:43:09	6875ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-07 14:02:21	4233ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-29 00:24:02	11245ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:43:48	11164ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:39:54	11260ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:15:43	1644ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:00:58	1822ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:22:40	1738ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:27:49	1819ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 07:21:03	2341ms	4 NS 0 A 0 MX	❓ Unknown