yzervision.dk

📜 Historical scan 2026-07-11 12:54:40 · ← Latest scan

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

yzervision.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 May 2007 (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 49ms

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#

132ms

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-14 05:40:25

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-05-02
Expires	2027-05-31 (221d)

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

49ms

60ms

40ms

AAAA

46ms

TXT

297ms

CAA

49ms

HTTPS

54ms

TLSA

75ms

SOA

34ms

MTA-STS

107ms

DNSSEC

132ms

SRV

161ms

Total

922ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 15:31:49	3944ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 14:10:08	1357ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:27:33	2945ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 14:42:27	7723ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 14:33:00	5491ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 14:31:45	5861ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:33:08	27321ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:07:32	8934ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:54:52	3068ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:18:36	1442ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:32:26	1013ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 15:06:52	2460ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:56:11	8718ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 21:45:57	890ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 21:27:58	2939ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 20:40:23	10139ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:56:43	2847ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 18:38:11	8724ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 07:23:42	755ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 02:02:26	897ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 22:28:57	740ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 20:32:04	992ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 19:08:35	8637ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 13:42:05	16668ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-13 04:44:18	939ms	2 NS 0 A 0 MX	❓ Unknown