vmaf2005.dk

📜 Historical scan 2026-07-23 05:03:29 · ← Latest scan

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

vmaf2005.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 6 May 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 this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 169ms

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#

199ms

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 00:37:57

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-05-06
Expires	2027-05-31 (216d)

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

169ms

164ms

118ms

AAAA

127ms

TXT

578ms

CAA

117ms

HTTPS

117ms

TLSA

113ms

SOA

24ms

MTA-STS

175ms

DNSSEC

199ms

SRV

170ms

Total

1327ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 06:27:42	1321ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-28 07:24:33	24752ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-19 16:23:41	49293ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 22:46:01	1385ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:12:05	3180ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:32:05	1739ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:25:19	944ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:15:23	1240ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 15:33:11	23673ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 15:30:54	54674ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 13:20:44	2533ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 05:29:51	24218ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:35:52	3359ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 19:53:42	1365ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 00:43:24	4194ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 18:48:56	2876ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 10:09:47	9657ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 02:15:47	956ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 11:49:01	1473ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:55:46	16678ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:35:14	10263ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:18:19	10119ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:34:33	854ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:03:29 shown	1327ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 17:10:14	920ms	2 NS 0 A 0 MX	❓ Unknown