vinges.dk

📜 Historical scan 2026-08-10 16:04:28 · ← Latest scan

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

vinges.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 5 July 2013 (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 179ms

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#

229ms

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 18:08:26

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-07-05
Expires	2029-07-31 (1007d)

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

179ms

206ms

198ms

AAAA

165ms

TXT

632ms

CAA

148ms

HTTPS

170ms

TLSA

121ms

SOA

70ms

MTA-STS

153ms

DNSSEC

229ms

SRV

201ms

Total

1535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 02:57:11	1265ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 19:48:09	1404ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:06:08	3462ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:05:54	2055ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:52:20	5372ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:50:14	2425ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 17:37:03	2009ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 17:36:22	26706ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 02:46:58	3008ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 11:44:42	2533ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 09:40:44	3161ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 04:15:56	4236ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 16:04:28 shown	1535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 11:06:37	27202ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 12:14:18	10201ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:15:50	9266ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:47:40	2828ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:13:17	10051ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:44:11	27344ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:21:26	1472ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:55:58	10037ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 05:41:31	933ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:20:10	16707ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 11:35:24	8676ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 10:08:45	858ms	2 NS 0 A 0 MX	❓ Unknown