writing-a-book.dk

📜 Historical scan 2026-07-27 23:24:12 · ← Latest scan

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

writing-a-book.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 2 June 2024 (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 56ms

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#

119ms

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-16 12:43:30

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2024-06-02
Expires	2027-06-01 (221d)

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

56ms

32ms

36ms

AAAA

60ms

TXT

181ms

CAA

35ms

HTTPS

63ms

TLSA

24ms

SOA

43ms

MTA-STS

105ms

DNSSEC

119ms

SRV

8060ms

Total

8631ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 11:25:10	26930ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 21:21:01	1581ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-22 21:05:51	35021ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 06:59:12	1552ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:24:34	3021ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:14:21	4876ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:09:46	846ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 16:46:01	16774ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 11:34:21	2341ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 11:32:58	10135ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 05:25:14	10163ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:19:54	27315ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 17:20:03	4917ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 08:10:03	1829ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 05:35:44	3073ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 00:04:28	10168ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 22:23:54	8671ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 07:45:47	948ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 20:55:30	1391ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:24:12 shown	8631ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:00:00	10023ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:10:47	10011ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:56:39	1414ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 20:04:05	1534ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 19:24:42	898ms	2 NS 0 A 0 MX	❓ Unknown