afdeling2.dk

📜 Historical scan 2026-08-20 20:24:28 · ← Latest scan

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

afdeling2.dk is a registered .dk domain whose nameservers (ns1.pil.dk, ns2.pil.dk, ns3.pil.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 28 November 2000 (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#

3 records 2227ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.pil.dk	185.126.152.22	chafpin.pil.dk	AS47527 DLX A/S
ns2.pil.dk	178.63.167.141 2a01:4f8:13b:2698::141	rixo.pil.dk rixo.pil.dk	AS24940 Hetzner Online GmbH AS24940 Hetzner Online GmbH
ns3.pil.dk	185.126.152.27	rontok.pil.dk	AS47527 DLX 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#

10085ms

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-14 04:03:25

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2000-11-28
Expires	2026-12-31 (66d)

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

2227ms

2215ms

AAAA

2212ms

TXT

3015ms

CAA

2220ms

HTTPS

2207ms

TLSA

4031ms

SOA

51ms

MTA-STS

4057ms

DNSSEC

10085ms

SRV

4056ms

Total

19522ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-21 14:38:58	2227ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:39:04	5491ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:51:51	4543ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:31:22	9245ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:24:28 shown	19522ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 20:10:01	2709ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:09:20	7292ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:08:32	2303ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 13:24:25	4521ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 18:51:36	1640ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:14:59	4845ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:17:20	4418ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 23:22:30	3369ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 19:16:03	1767ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 04:34:14	3140ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-04 04:30:05	9748ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 01:23:45	2559ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 07:01:09	2130ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:31:12	1924ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:45:58	1987ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:21:22	1696ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 01:12:18	10680ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:53:30	1901ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:43:32	9207ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 04:55:12	2029ms	3 NS 0 A 0 MX	❓ Unknown