fyrodanvvs.dk

📜 Historical scan 2026-08-14 20:24:32 · ← Latest scan

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

fyrodanvvs.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 4 October 2004 (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 688ms

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#

728ms

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-20 08:15:37

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-10-04
Expires	2027-10-31 (375d)

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

688ms

679ms

681ms

AAAA

686ms

TXT

3381ms

CAA

686ms

HTTPS

679ms

TLSA

676ms

SOA

40ms

MTA-STS

700ms

DNSSEC

728ms

SRV

748ms

Total

6561ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 12:49:55	5650ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:41:37	5759ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:57:28	10361ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:40:32	10611ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:37:25	3599ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:37:01	4509ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:28:19	10413ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:21:46	6243ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 20:24:32 shown	6561ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 22:45:41	13126ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 20:37:01	4158ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 15:53:31	9382ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 08:05:37	6624ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 18:44:39	6527ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 10:57:03	12703ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 23:23:58	12696ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:33:54	17977ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 20:09:45	10350ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:48:25	18007ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 19:34:03	6479ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:49:07	13746ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:21:22	6464ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 02:05:46	9709ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:57:45	2617ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 22:30:44	18290ms	3 NS 0 A 0 MX	❓ Unknown