werlauff-publishing.dk

📜 Historical scan 2026-08-19 03:46:29 · ← Latest scan

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

werlauff-publishing.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 16 October 2020 (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 103ms

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#

552ms

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-15 20:48:48

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2020-10-16
Expires	2026-10-31 (14d)

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

103ms

191ms

151ms

AAAA

167ms

TXT

558ms

CAA

97ms

HTTPS

133ms

TLSA

156ms

SOA

73ms

MTA-STS

8294ms

DNSSEC

552ms

SRV

251ms

Total

10558ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 23:17:58	1213ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 23:12:25	1670ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:03:51	2043ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:44:34	4051ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:36:41	4070ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:03:33	10363ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:46:29 shown	10558ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:38:28	3582ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 22:26:59	2943ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 05:32:41	3159ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:17:14	2951ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 18:08:39	911ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 17:48:59	10074ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 05:10:10	857ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 23:02:58	1505ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 19:50:00	908ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 18:33:54	9997ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:12:55	16626ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:40:30	10061ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:17:51	32666ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:16:52	32176ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:04:09	915ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 21:45:36	926ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 10:40:02	1547ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 04:24:23	806ms	2 NS 0 A 0 MX	❓ Unknown