dirchsen.dk

📜 Historical scan 2026-08-15 04:59:54 · ← Latest scan

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

dirchsen.dk is a registered .dk domain whose nameservers (tix.ns.tele.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 March 1998 (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#

1 records 253ms

Nameserver	IP addresses	PTR	ASN / ISP
tix.ns.tele.dk	193.162.145.130 2001:6c8:4:100::53	tix.ns.tele.dk tix.ns.tele.dk	AS3292 TDC Holding A/S AS3292 TDC Holding 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#

465ms

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-14 02:27:25

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	1998-03-03
Expires	2027-03-31 (161d)

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

253ms

298ms

293ms

AAAA

251ms

TXT

826ms

CAA

312ms

HTTPS

347ms

TLSA

106ms

SOA

164ms

MTA-STS

388ms

DNSSEC

465ms

SRV

341ms

Total

3117ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 18:21:55	2735ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-27 17:11:08	1283ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-13 13:14:35	1183ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-27 04:25:11	9991ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-24 11:13:00	1024ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:53:17	10101ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:29:53	1062ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:19:42	9841ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:38:07	974ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-19 01:24:25	1107ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-17 19:41:04	941ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:07:35	1886ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-15 04:59:54 shown	3117ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:42:47	2813ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-12 08:29:12	1129ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:31:49	2009ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-07 14:24:53	982ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-03 14:45:19	1875ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-29 04:43:19	10352ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:19:32	2963ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-26 16:06:44	8696ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-25 15:17:51	2696ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:42:56	754ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:19:05	826ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:33:34	840ms	1 NS 0 A 0 MX	❓ Unknown