skipperogkonen.dk

📜 Historical scan 2026-08-17 22:41:56 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Record History ⚡ Scan Now

skipperogkonen.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 22 February 2018 (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 41ms

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

123ms

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-02 15:30:27

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2018-02-22
Expires	2027-02-28 (148d)

📋 WHOIS

⏱️ Lookup Timing

41ms

47ms

40ms

AAAA

46ms

TXT

299ms

CAA

41ms

HTTPS

36ms

TLSA

28ms

SOA

23ms

MTA-STS

128ms

DNSSEC

123ms

SRV

128ms

Total

781ms

🕐 Scan History

Scanned At	Duration	Records	DNSSEC
2026-10-02 11:33:43	102ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-01 11:33:35	347ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-30 11:18:28	686ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-02 03:47:55	1419ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 04:29:10	843ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:26:46	17199ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:13:59	1453ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:01:22	10269ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:00:25	6142ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:21:39	3329ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:41:56 shown	781ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 20:21:24	10182ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 15:35:05	1418ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 20:13:05	803ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 15:17:36	27227ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 22:14:46	2465ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 05:33:07	1037ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 20:31:11	10072ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 04:23:43	45777ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:00:06	1216ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 03:28:16	988ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:04:50	1067ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 02:39:16	783ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 23:51:01	1112ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:28:21	1125ms	2 NS 0 A 0 MX	❓ Unknown