rez.dk

📜 Historical scan 2026-08-18 05:44:08 · ← Latest scan

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

rez.dk is a registered .dk domain whose nameservers (ns1.dnsatconviator.com, ns2.dnsatconviator.com, ns3.dnsatconviator.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 24 May 2024 (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#

3 records 972ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dnsatconviator.com	185.106.119.62	ns1.dnsatconviator.com	AS201926 VK DATA ApS
ns2.dnsatconviator.com	185.106.119.63	ns2.dnsatconviator.com	AS201926 VK DATA ApS
ns3.dnsatconviator.com	185.106.119.64	ns3.dnsatconviator.com	AS201926 VK DATA ApS

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

1022ms

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-16 12:47:44

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2024-05-24
Expires	2027-05-23 (214d)

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

972ms

897ms

980ms

AAAA

975ms

TXT

4129ms

CAA

984ms

HTTPS

900ms

TLSA

712ms

SOA

206ms

MTA-STS

1007ms

DNSSEC

1022ms

SRV

916ms

Total

8442ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 16:10:26	6411ms	3 NS 0 A 0 MX	❓ Unknown
2026-10-02 23:32:16	5837ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:55:22	9942ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:54:20	3752ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:49:05	6712ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:31:45	11345ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:11:43	5289ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 05:44:08 shown	8442ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 23:09:36	8429ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 02:43:25	7048ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 15:20:24	13592ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 14:03:34	8730ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 11:24:22	17364ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 15:58:55	6548ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-05 11:21:55	7694ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 04:02:25	8276ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 17:04:58	6393ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:39:41	3511ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:11:26	17736ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:40:03	13823ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:29:56	4430ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:45:21	4510ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 01:11:32	3626ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:01:30	3133ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:22:46	3919ms	3 NS 0 A 0 MX	❓ Unknown