westrin.dk

📜 Historical scan 2026-07-18 14:01:39 · ← Latest scan

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

westrin.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 9 September 2011 (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 105ms

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#

158ms

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-13 12:56:10

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-09-09
Expires	2028-09-30 (706d)

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

105ms

98ms

90ms

AAAA

85ms

TXT

398ms

CAA

83ms

HTTPS

104ms

TLSA

55ms

SOA

35ms

MTA-STS

131ms

DNSSEC

158ms

SRV

121ms

Total

946ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 13:36:57	1481ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 16:15:12	9991ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 10:59:15	2865ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:05:36	5164ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:55:59	4972ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:29:24	3772ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:54:22	4848ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 23:05:33	3928ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 07:10:31	10123ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 03:01:18	1498ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:10:32	3810ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 10:28:38	27239ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 20:12:31	2500ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 06:33:08	1679ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 10:21:07	1469ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:53:39	8896ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:11:31	957ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:26:06	983ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 12:11:52	905ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:45:41	982ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 08:13:10	928ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:39:33	1072ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 19:45:54	9996ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 14:01:39 shown	946ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 13:25:37	948ms	2 NS 0 A 0 MX	❓ Unknown