sigurdh.dk

📜 Historical scan 2026-07-04 15:23:43 · ← Latest scan

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

sigurdh.dk is a registered .dk domain whose nameservers (ns1.mlhosting.eu, ns2.mlhosting.eu) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 27 October 2005 (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 106ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.mlhosting.eu	—	—	—
ns2.mlhosting.eu	—	—	—

🌍 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-07 21:36:00

www	194.45.78.71 (AS204151) (address records, no CNAME)
www vs bare domain	Same network sigurdh.dk: 194.45.78.71 (AS204151) www.sigurdh.dk: 194.45.78.71 (AS204151)
Wildcard	Yes: any name under the zone resolves

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

145ms

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-18 13:50:04

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2005-10-27
Expires	2027-10-31 (376d)

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

106ms

74ms

73ms

AAAA

140ms

TXT

350ms

CAA

104ms

HTTPS

81ms

TLSA

60ms

SOA

123ms

MTA-STS

62ms

DNSSEC

145ms

SRV

328ms

Total

1098ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 21:36:00	401ms	2 NS 1 A 0 MX	🔓 Insecure
2026-10-01 06:27:35	589ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-15 06:54:23	1107ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-11 09:20:39	1809ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-26 04:37:48	719ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-15 11:35:05	986ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-10 13:34:39	919ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-08 22:59:00	1368ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-06 14:17:59	2131ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-04 15:23:43 shown	1098ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-03 01:30:26	643ms	2 NS 0 A 0 MX	❓ Unknown
2026-06-24 09:35:24	3082ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-24 03:24:48	1164ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-23 19:58:40	3310ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-22 17:46:27	3144ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-21 18:26:04	1150ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-19 16:55:26	892ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-19 01:11:01	802ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-17 19:24:41	5061ms	0 NS 0 A 0 MX	❓ Unknown