siersted.dk

📜 Historical scan 2026-07-22 23:54:41 · ← Latest scan

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

siersted.dk is a registered .dk domain whose nameservers (ns1.ascio.net, ns2.ascio.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 April 2001 (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 105ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.ascio.net	156.154.130.100 2610:a1:1022::100	ns0.netnames.net spdns3.cscdns.net	AS12008 Vercara, LLC AS12008 Vercara, LLC
ns2.ascio.net	156.154.131.100 2610:a1:1023::100	h.ns-bac.org ns4.netnames.net	AS12008 Vercara, LLC AS12008 Vercara, LLC

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

157ms

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-20 08:30:44

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-04-05
Expires	2027-06-30 (252d)

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

105ms

87ms

103ms

AAAA

93ms

TXT

469ms

CAA

82ms

HTTPS

88ms

TLSA

187ms

SOA

11ms

MTA-STS

83ms

DNSSEC

157ms

SRV

170ms

Total

1327ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-26 07:04:47	10987ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:00:13	4416ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:45:30	7790ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:15:11	1565ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:39:34	1481ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:12:21	1319ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 06:43:23	4014ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 20:06:30	10948ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 11:11:55	3500ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:39:57	11282ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:23:48	1603ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 09:26:36	1517ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 07:59:09	2851ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:22:05	3437ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:11:37	10923ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:44:30	1247ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:30:37	1278ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:04:58	9168ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 23:54:41 shown	1327ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 20:47:49	3888ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 05:44:31	10843ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 00:33:15	10851ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 23:48:00	9315ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 23:01:02	11044ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 18:38:34	1146ms	2 NS 0 A 0 MX	❓ Unknown