pd.dk

📜 Historical scan 2026-07-22 06:41:42 · ← Latest scan

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

pd.dk is a registered .dk domain whose nameservers (dns101.telia.com, dns102.telia.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 23 August 1996 (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 214ms

Nameserver	IP addresses	PTR	ASN / ISP
dns101.telia.com	194.255.56.69 2001:2011:c000::2	dns101.telia.com dns101.telia.com	AS3308 Norlys Telco A/S AS3308 Norlys Telco A/S
dns102.telia.com	194.255.56.70 2001:2011:c000:1::2	dns102.telia.com dns102.telia.com	AS3308 Norlys Telco A/S AS3308 Norlys Telco 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#

293ms

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-17 12:08:04

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	1996-08-23
Expires	2027-09-30 (347d)

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

214ms

259ms

180ms

AAAA

216ms

TXT

286ms

CAA

122ms

HTTPS

149ms

TLSA

49ms

SOA

23ms

MTA-STS

211ms

DNSSEC

293ms

SRV

258ms

Total

980ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 03:07:55	1544ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-02 18:01:34	1679ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 11:18:13	3250ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:57:54	1852ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:49:42	1724ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:46:34	1604ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:57:49	1614ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:01:58	2080ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:37:43	1982ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:30:07	4048ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 05:07:09	10449ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 22:55:06	1795ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 21:54:05	3009ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 01:57:02	10455ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 20:33:25	2805ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 06:46:42	2825ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:57:53	10295ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:45:24	1420ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 09:34:18	10298ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 09:28:19	1305ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 08:54:33	1132ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:41:42 shown	980ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 03:15:54	10467ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 18:48:33	3153ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 17:56:22	17108ms	2 NS 0 A 0 MX	❓ Unknown