vinkuppet.dk

Records from scan: 2026-09-03 15:32:52 · 9935ms total · last checked 2026-10-27 19:30 (unchanged)

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

vinkuppet.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 September 2008 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 182ms

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#

9184ms

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-27 23:55:39

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-09-02
Expires	2027-09-30 (337d)

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

182ms

183ms

AAAA

132ms

TXT

699ms

CAA

182ms

HTTPS

135ms

TLSA

114ms

SOA

34ms

MTA-STS

147ms

DNSSEC

9184ms

SRV

184ms

Total

9935ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-03 15:32:52 shown	9935ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:27:07	2907ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:16:29	908ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:11:02	1267ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 14:56:35	955ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 14:40:35	4570ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 14:36:41	2819ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:50:16	1521ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 07:17:08	3202ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 20:39:00	1535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 00:46:53	3202ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:37:10	29405ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 14:08:56	10082ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 00:06:08	1427ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 06:40:07	6270ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:32:18	928ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:57:46	941ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:25:09	933ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:54:48	1405ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 20:56:47	917ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 18:44:10	982ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 05:11:54	10006ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 00:31:25	1037ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:36:35	1061ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 23:18:20	8730ms	2 NS 0 A 0 MX	❓ Unknown