yetz.dk

📜 Historical scan 2026-08-20 09:53:03 · ← Latest scan

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

yetz.dk is a registered .dk domain whose nameservers (ns01.no.brand.one.com, ns02.no.brand.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 March 2017 (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 73ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.no.brand.one.com	195.206.121.12 2001:67c:28cc::12	ns01.no.brand.one.com ns01.no.brand.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.no.brand.one.com	185.10.11.12 2001:67c:3c0::12	ns02.no.brand.one.com ns02.no.brand.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#

384ms

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-15 22:25:51

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-03-06
Expires	2027-03-31 (159d)

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

73ms

91ms

84ms

AAAA

75ms

TXT

348ms

CAA

105ms

HTTPS

92ms

TLSA

118ms

SOA

76ms

MTA-STS

118ms

DNSSEC

384ms

SRV

960ms

Total

2170ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 04:41:28	1292ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:38:52	3521ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:31:38	10197ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:26:42	16846ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:53:03 shown	2170ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:33:05	10482ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:04:00	3107ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 07:14:19	27249ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 15:39:59	6272ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:04:22	2685ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 19:42:39	8820ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 15:29:11	3869ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 08:18:37	1967ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 05:19:30	751ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 13:44:44	1593ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:35:31	8616ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 12:44:10	801ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:09:27	1396ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:41:40	1064ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:03:23	956ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:25:55	10019ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 19:01:06	1153ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 14:13:38	27162ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 12:29:49	14045ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 04:57:40	935ms	2 NS 0 A 0 MX	❓ Unknown