flaskesamlerne.dk

📜 Historical scan 2026-07-04 10:43:20 · ← Latest scan

🚫 Deactivated by the registry ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

flaskesamlerne.dk is a .dk domain the registry has taken out of service: it is delegated to the registry's own sentinel nameservers (nonexistent.punktum.dk), so it does not resolve. It 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#

1 records 29ms

Nameserver	IP addresses	PTR	ASN / ISP
nonexistent.punktum.dk	—	—	—

🌍 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-08 07:07:40

www	94.231.103.54 (AS48854) (address records, no CNAME)
www vs bare domain	Same network flaskesamlerne.dk: 94.231.103.54 (AS48854) www.flaskesamlerne.dk: 94.231.103.54 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

124ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

29ms

45ms

32ms

AAAA

42ms

TXT

87ms

CAA

44ms

HTTPS

40ms

TLSA

14ms

SOA

27ms

MTA-STS

46ms

DNSSEC

124ms

SRV

46ms

Total

542ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 04:35:59	626ms	4 NS 1 A 0 MX	🔒 Secure
2026-10-01 04:30:53	429ms	4 NS 1 A 0 MX	🔒 Secure
2026-09-25 17:09:17	436ms	4 NS 1 A 0 MX	🔒 Secure
2026-09-16 09:44:08	464ms	4 NS 1 A 0 MX	🔒 Secure
2026-07-28 01:38:09	657ms	4 NS 1 A 0 MX	🔒 Secure
2026-07-27 01:01:40	793ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:33:25	788ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-25 00:02:28	696ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-23 23:33:10	1132ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:21:43	662ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-21 14:47:49	655ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-19 22:22:58	975ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-18 16:07:35	8594ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-17 12:40:33	701ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-16 06:34:12	954ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-14 00:26:28	677ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-08 14:03:22	992ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-06 19:00:35	778ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-05 15:12:12	1061ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-04 10:43:20 shown	542ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-03 12:58:33	2995ms	1 NS 0 A 0 MX	❓ Unknown
2026-06-20 08:37:34	378ms	4 NS 1 A 0 MX	🔒 Secure
2026-06-17 09:34:51	431ms	4 NS 1 A 0 MX	🔒 Secure