stutteriskyttegaarden.dk

📜 Historical scan 2026-08-19 16:41:45 · ← Latest scan

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

stutteriskyttegaarden.dk is a registered .dk domain whose nameservers (ns4.123hjemmeside.dk, ns5.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 October 2008 (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 4267ms

Nameserver	IP addresses	PTR	ASN / ISP
ns4.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns5.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 Amazon.com, 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#

10726ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-23 00:59:36

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-10-06
Expires	2027-10-31 (372d)

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

4267ms

4261ms

AAAA

4298ms

TXT

16736ms

CAA

4286ms

HTTPS

4267ms

TLSA

4185ms

SOA

4313ms

MTA-STS

4351ms

DNSSEC

10726ms

SRV

4316ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-23 19:17:12	64919ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-22 02:14:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 18:56:32	61014ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-15 11:53:44	57303ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 14:01:05	58216ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 12:55:29	61391ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:04:57	63389ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:21:06	61648ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:15:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:07:56	57402ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 16:41:45 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 16:36:23	58783ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:09:37	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 20:44:17	61306ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 08:52:46	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 07:04:59	58384ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:04:51	59279ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 07:49:29	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 04:00:49	59325ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 04:17:56	57265ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 15:33:50	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 14:19:09	63402ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:32:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:10:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:52:06	65535ms	2 NS 0 A 0 MX	❓ Unknown