98oktan.dk

📜 Historical scan 2026-08-05 21:57:20 · ← Latest scan

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

98oktan.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 8 May 2001 (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 169ms

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#

220ms

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-20 14:25:56

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-05-08
Expires	2027-06-30 (249d)

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

169ms

141ms

172ms

AAAA

175ms

TXT

642ms

CAA

186ms

HTTPS

148ms

TLSA

114ms

SOA

26ms

MTA-STS

191ms

DNSSEC

220ms

SRV

183ms

Total

1396ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-03 20:32:46	55293ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:44:30	8959ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:37:55	1366ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:35:39	4386ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:23:56	4314ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 13:52:24	27371ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 13:49:01	22709ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 19:23:42	1052ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 15:36:37	888ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 18:14:09	4712ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 20:10:58	4961ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 21:57:20 shown	1396ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 22:42:34	38242ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 09:52:00	774ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 18:42:50	1402ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 14:24:55	1428ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:38:52	1089ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 12:09:34	1001ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:30:51	2566ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:29:09	948ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:15:12	1007ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:02:52	8967ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 22:59:56	10031ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 10:17:18	1021ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 07:58:47	1029ms	2 NS 0 A 0 MX	❓ Unknown