69884887.dk

📜 Historical scan 2026-07-30 14:47:24 · ← Latest scan

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

69884887.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 4 October 2019 (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 4028ms

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#

10058ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-19 13:33:43

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-10-04
Expires	2027-10-31 (373d)

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

4028ms

4030ms

AAAA

4027ms

TXT

20129ms

CAA

4028ms

HTTPS

4029ms

TLSA

2026ms

SOA

4026ms

MTA-STS

4038ms

DNSSEC

10058ms

SRV

4030ms

Total

51300ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-22 15:51:55	1771ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-30 00:16:09	1244ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-06 21:22:29	2787ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-28 00:14:36	1403ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 07:44:55	4917ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 07:31:18	1141ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 07:16:16	5619ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 06:56:40	17186ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 05:04:10	854ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 04:40:55	1487ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 16:26:30	10211ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 12:03:04	25007ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 09:31:56	25371ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:49:02	24539ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:02:54	3004ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 04:47:13	3320ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-08 02:21:47	3005ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-30 14:47:24 shown	51300ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 01:36:31	671ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 00:16:33	695ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 23:29:59	1343ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 23:07:09	1174ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 22:49:48	694ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 21:37:51	734ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 02:40:51	1423ms	2 NS 0 A 0 MX	⚠️ Bogus