wootton.dk

📜 Historical scan 2026-08-07 08:42:22 · ← Latest scan

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

wootton.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 1 June 2004 (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 39ms

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#

125ms

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-23 20:13:33

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-06-01
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#

39ms

44ms

48ms

AAAA

53ms

TXT

363ms

CAA

32ms

HTTPS

54ms

TLSA

39ms

SOA

40ms

MTA-STS

123ms

DNSSEC

125ms

SRV

132ms

Total

993ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-28 07:39:09	1310ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-10 21:16:12	1308ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 09:16:47	2953ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:12:18	3058ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 08:55:07	10329ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:47:22	1244ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:57:23	1183ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:46:18	5500ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:39:27	2362ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:04:02	1910ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:32:46	2674ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 17:42:39	10207ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 15:37:25	28194ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:40:41	3748ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 14:09:57	845ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 08:42:22 shown	993ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 01:34:13	1494ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 23:32:22	27318ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 17:14:34	8855ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 08:35:34	35160ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:22:50	2266ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:56:52	10085ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 21:28:35	910ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:39:55	855ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 20:32:42	984ms	2 NS 0 A 0 MX	❓ Unknown