aleader.dk

📜 Historical scan 2026-08-12 02:15:58 · ← Latest scan

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

aleader.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 1 October 2014 (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 4127ms

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#

10328ms

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-13 01:30:01

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-10-01
Expires	2026-10-31 (3d)

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

4127ms

4184ms

4183ms

AAAA

4167ms

TXT

16282ms

CAA

4173ms

HTTPS

4130ms

TLSA

2150ms

SOA

4177ms

MTA-STS

4199ms

DNSSEC

10328ms

SRV

4193ms

Total

49512ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-22 05:44:26	1797ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-08 01:22:17	1259ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 23:55:39	1453ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:17:30	8808ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 05:36:03	8915ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:09:42	29820ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:06:06	1399ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:47:47	1474ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:53:31	2140ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:21:07	8704ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 04:24:26	2319ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:21:28	4111ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 05:01:42	22754ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:15:58 shown	49512ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 23:06:17	26997ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 23:20:12	27262ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 03:56:47	924ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 15:24:49	935ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 12:52:53	10081ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 10:03:49	1397ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 01:52:06	907ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 01:36:41	10011ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:21:34	984ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:09:46	995ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:59:00	880ms	2 NS 0 A 0 MX	❓ Unknown