dilipop.dk

📜 Historical scan 2026-09-26 00:48:29 · ← Latest scan

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

dilipop.dk is a registered .dk domain whose nameservers (dns106.ovh.net, ns106.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 11 September 2013 (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 436ms

Nameserver	IP addresses	PTR	ASN / ISP
dns106.ovh.net	2001:41d0:d01::2 5.196.41.1	dns106.ovh.net dns106.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns106.ovh.net	2001:41d0:b00:fa00::2 5.135.65.21	ns106.ovh.net ns106.ovh.net	AS16276 OVH SAS AS16276 OVH SAS

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

9429ms

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-19 16:50:43

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-09-11
Expires	2027-09-30 (345d)

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

436ms

431ms

437ms

AAAA

435ms

TXT

1879ms

CAA

375ms

HTTPS

431ms

TLSA

366ms

SOA

35ms

MTA-STS

385ms

DNSSEC

9429ms

SRV

449ms

Total

12536ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 03:59:39	4167ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 00:48:29 shown	12536ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 12:21:29	5547ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:30:21	10949ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:00:10	3808ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 10:08:35	4716ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:16:58	6268ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 06:14:21	3207ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:58:10	30987ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 20:02:59	5935ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 19:54:43	6124ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:29:20	3868ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 09:41:49	4107ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 00:22:01	6329ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 06:52:08	15048ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 19:46:29	3830ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:18:26	1798ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:01:14	15611ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:40:14	3717ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:26:10	7468ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:58:43	17164ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:12:11	11513ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:58:17	9981ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:23:52	6550ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 03:52:52	13269ms	2 NS 0 A 0 MX	❓ Unknown