1-hjaelp.dk

📜 Historical scan 2026-07-19 23:03:36 · ← Latest scan

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

1-hjaelp.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 March 2017 (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 37ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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#

108ms

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-12 11:30:57

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-03-09
Expires	2027-03-31 (165d)

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

37ms

42ms

AAAA

37ms

TXT

156ms

CAA

36ms

HTTPS

37ms

TLSA

62ms

SOA

34ms

MTA-STS

70ms

DNSSEC

108ms

SRV

16042ms

Total

16642ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-05 09:59:07	1435ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:30:36	3187ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 16:21:27	3612ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 16:04:47	3985ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:57:14	1538ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 15:10:13	1669ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 15:03:52	4245ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:14:22	3939ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:31:40	3065ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 08:10:25	3036ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 14:00:25	10225ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 02:28:38	2603ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 22:20:13	1417ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 21:09:30	53393ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 00:44:42	31148ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 16:51:47	8593ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:28:36	9020ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 15:00:37	8698ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:40:24	1602ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:02:41	8739ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 11:07:01	807ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 04:07:15	29298ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 23:03:36 shown	16642ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 22:40:39	776ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 22:17:16	1083ms	2 NS 0 A 0 MX	❓ Unknown