supersanne.dk

📜 Historical scan 2026-08-26 21:23:41 · ← Latest scan

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

supersanne.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 2 October 2006 (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 720ms

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#

716ms

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-19 10:29:39

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-10-02
Expires	2027-10-31 (376d)

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

720ms

732ms

648ms

AAAA

728ms

TXT

3198ms

CAA

642ms

HTTPS

729ms

TLSA

631ms

SOA

69ms

MTA-STS

676ms

DNSSEC

716ms

SRV

730ms

Total

6291ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 07:28:38	6610ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-20 15:23:14	13961ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-26 21:23:41 shown	6291ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:47:23	7267ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:56:18	6227ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:38:23	9564ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 13:37:34	5744ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:45:25	6238ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:39:45	8142ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:50:22	9020ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:12:28	5042ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 07:24:15	8682ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 05:22:46	13942ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:57:31	7637ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 08:25:04	6517ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 19:50:50	11728ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:20:01	6088ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:52:10	2626ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:20:57	3697ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:44:02	3296ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:39:04	6001ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:29:54	3550ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 15:22:52	13165ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 13:10:01	6450ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:58:29	2815ms	3 NS 0 A 0 MX	❓ Unknown