helmuthdegn.dk

📜 Historical scan 2026-08-22 10:05:38 · ← Latest scan

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

helmuthdegn.dk is a registered .dk domain whose nameservers (ns1.123hjemmeside.dk, ns2.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 July 2007 (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 4391ms

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

10663ms

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-16 14:46:42

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-07-13
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#

4391ms

4345ms

4354ms

AAAA

4374ms

TXT

17013ms

CAA

4328ms

HTTPS

4404ms

TLSA

4134ms

SOA

4374ms

MTA-STS

4477ms

DNSSEC

10663ms

SRV

4438ms

Total

61877ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 04:42:18	63265ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 03:25:24	57294ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 12:38:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 10:45:29	59371ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:05:38 shown	61877ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:58:59	64180ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:28:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:24:28	62620ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 02:32:14	63412ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:35:39	63187ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 12:47:22	56134ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 22:17:29	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 14:47:44	58003ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:41:25	57401ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 15:28:28	61298ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 07:13:05	63398ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 10:12:50	57441ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 05:56:48	57236ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:08:50	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:00:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:49:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:35:16	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:22:32	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 01:13:12	59204ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 09:38:46	65535ms	2 NS 0 A 0 MX	❓ Unknown