vinketv.dk

📜 Historical scan 2026-08-21 12:32:41 · ← Latest scan

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

vinketv.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 3 June 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 58ms

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#

8191ms

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-18 14:23:28

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-06-03
Expires	2027-06-30 (245d)

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

58ms

76ms

87ms

AAAA

61ms

TXT

294ms

CAA

77ms

HTTPS

76ms

TLSA

87ms

SOA

59ms

MTA-STS

116ms

DNSSEC

8191ms

SRV

151ms

Total

9110ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 15:59:02	1303ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 05:01:14	1372ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-23 13:11:26	1304ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 05:36:22	10031ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:14:20	2639ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:59:30	987ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:32:41 shown	9110ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:26:15	5348ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:10:00	1472ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:59:29	9014ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:27:49	3994ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 12:20:26	2882ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 01:46:23	3605ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:19:07	4291ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 09:43:57	8717ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 18:27:14	1410ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 19:02:49	1525ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 14:41:43	810ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:45:04	10403ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 13:01:53	618ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 12:40:51	739ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:18:45	1436ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 10:32:50	2500ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 22:54:27	943ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 09:22:33	681ms	2 NS 0 A 0 MX	❓ Unknown