stokkebysmede.dk

📜 Historical scan 2026-08-20 15:05:16 · ← Latest scan

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

stokkebysmede.dk is a registered .dk domain whose nameservers (ns1.dnsservers.dk, ns2.dnsservers.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 4 July 2011 (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 502ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dnsservers.dk	2001:1448:0:a800::53 217.30.38.181	authns1.ngdc.net dns1.sentia.dk	AS47292 Sentia Denmark A/S AS47292 Sentia Denmark A/S
ns2.dnsservers.dk	2001:1448:0:a500::53 217.30.38.27	authns2.ngdc.net dns2.sentia.dk	AS47292 Sentia Denmark A/S AS47292 Sentia 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#

3624ms

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-16 23:08:37

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-07-04
Expires	2027-07-31 (281d)

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

502ms

697ms

477ms

AAAA

4390ms

TXT

15030ms

CAA

1908ms

HTTPS

667ms

TLSA

128ms

SOA

217ms

MTA-STS

4412ms

DNSSEC

3624ms

SRV

4380ms

Total

23843ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 17:31:40	26351ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 15:55:46	24358ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:20:29	27995ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:12:15	41839ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:05:16 shown	23843ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:05:23	2594ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 02:07:21	22496ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:04:04	26654ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:11:35	23498ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 12:42:45	989ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 11:38:14	21506ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 04:53:32	21548ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:52:42	24382ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 01:42:09	22487ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 20:34:41	25071ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 18:12:57	1231ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:28:41	27524ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:44:35	24109ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:22:40	23207ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:51:41	8844ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:50:20	23400ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:04:46	6222ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 12:43:59	1164ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 02:58:33	1499ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 02:45:55	1627ms	2 NS 0 A 0 MX	❓ Unknown