herluf-chr-jensen.dk

📜 Historical scan 2026-07-21 03:29:39 · ← Latest scan

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

herluf-chr-jensen.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 2 June 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 4105ms

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#

10342ms

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 13:56:20

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-06-02
Expires	2027-06-30 (249d)

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

4105ms

4131ms

4251ms

AAAA

4233ms

TXT

16361ms

CAA

4094ms

HTTPS

4092ms

TLSA

4026ms

SOA

4250ms

MTA-STS

4219ms

DNSSEC

10342ms

SRV

4248ms

Total

57732ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-28 02:38:26	61580ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 00:42:16	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:50:27	59415ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:47:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:36:02	61729ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:45:30	62277ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:30:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:05:26	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:09:07	62308ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 13:28:09	61401ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 11:10:31	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 05:50:57	63306ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 15:25:54	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 11:16:00	64508ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 09:15:12	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 22:58:30	63193ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 14:57:37	61003ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:39:08	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:09:37	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 13:49:33	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:04:31	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:02:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 03:29:39 shown	57732ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 22:54:44	65287ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 21:29:29	61223ms	2 NS 0 A 0 MX	❓ Unknown