setpace.dk

📜 Historical scan 2026-08-24 00:05:01 · ← Latest scan

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

setpace.dk is a registered .dk domain whose nameservers (ns1.fsdatans.net, ns2.fsdatans.net, ns3.fsdatans.net 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 46ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.fsdatans.net	162.159.24.16 2400:cb00:2049:1::a29f:1810	ns1.fsdatans.net —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns2.fsdatans.net	162.159.25.37 2400:cb00:2049:1::a29f:1925	ns2.fsdatans.net —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns3.fsdatans.net	162.159.24.16 2400:cb00:2049:1::a29f:1810	ns1.fsdatans.net —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns4.fsdatans.net	162.159.25.37 2400:cb00:2049:1::a29f:1925	ns2.fsdatans.net —	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#

132ms

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#

46ms

64ms

56ms

AAAA

43ms

TXT

209ms

CAA

61ms

HTTPS

39ms

TLSA

207ms

SOA

26ms

MTA-STS

149ms

DNSSEC

132ms

SRV

431ms

Total

1680ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-26 12:34:32	4057ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-24 00:05:01 shown	1680ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 21:26:28	1302ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 21:21:02	8688ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 21:15:47	2577ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 20:53:12	2205ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:46:36	1608ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 22:04:50	3834ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 10:38:19	4150ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-14 07:30:42	1982ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 07:37:45	3932ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:57:50	3676ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-08 14:56:50	10745ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-31 23:48:58	1638ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-30 01:11:28	3208ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-28 19:05:36	11151ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:47:50	2479ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 16:43:52	13301ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:40:32	18719ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:31:05	17543ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:09:42	10601ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:33:30	2122ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:11:15	2170ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-20 05:00:18	2589ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-18 06:16:23	2341ms	4 NS 0 A 0 MX	❓ Unknown