vinjensen.dk

📜 Historical scan 2026-08-09 09:27:53 · ← Latest scan

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

vinjensen.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 8 January 2002 (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 72ms

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#

174ms

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-11 11:41:35

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2002-01-08
Expires	2027-03-31 (154d)

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

72ms

94ms

56ms

AAAA

68ms

TXT

230ms

CAA

72ms

HTTPS

80ms

TLSA

74ms

SOA

43ms

MTA-STS

114ms

DNSSEC

174ms

SRV

148ms

Total

804ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-04 10:16:10	1217ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 21:32:09	1406ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 09:26:19	28982ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 06:05:01	1492ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 02:56:40	4174ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 02:44:09	4969ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:33:40	1610ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 01:55:46	1290ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:02:28	3958ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 15:11:26	3878ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 09:05:12	2765ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 05:24:19	3304ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 00:17:18	10091ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:35:10	3582ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 09:27:53 shown	804ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 01:23:42	778ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:41:28	23402ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 14:51:29	34476ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 14:00:19	2877ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 07:37:43	2824ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 13:20:36	1526ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 01:41:32	1393ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 01:16:13	899ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:52:21	1132ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 00:44:56	976ms	2 NS 0 A 0 MX	❓ Unknown