glowingcookies.dk

📜 Historical scan 2026-06-23 14:37:14 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

glowingcookies.dk is a .dk domain with no delegation in this scan. It was registered on 4 June 2018 (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#

🖥️

No NS records found

🌍 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-14 03:44:15

www	80.209.104.164 (AS44869) (address records, no CNAME)
www vs bare domain	Same network glowingcookies.dk: 80.209.104.164 (AS44869) www.glowingcookies.dk: 80.209.104.164 (AS44869)
Wildcard	No
Denial of existence	Compact NSEC (RFC 9824, "black lies") not walkable
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#

293ms

Check	Result
Validation Status	Not applicable: the domain has no delegation, so there is no zone to validate (stored verdict: ❓ Unknown).
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-14 04:15:37

Field	Value
Registrar	Simply.com A/S
Registered	2018-06-04
Expires	2027-06-30 (249d)

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

206ms

156ms

AAAA

203ms

TXT

295ms

CAA

206ms

HTTPS

201ms

TLSA

18ms

SOA

215ms

MTA-STS

209ms

DNSSEC

293ms

SRV

208ms

Total

909ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-14 03:44:15	1826ms	2 NS 1 A 0 MX	🔓 Insecure
2026-10-01 05:08:59	779ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-30 09:39:12	431ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-23 21:45:12	608ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-19 10:57:51	631ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-27 09:49:43	2427ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-27 00:16:19	777ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-25 23:10:20	1016ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-21 12:34:56	3335ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-20 12:08:15	6344ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-18 09:59:29	4887ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-02 21:03:54	852ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-22 19:17:05	846ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-09 19:54:39	857ms	2 NS 1 A 0 MX	🔓 Insecure
2026-06-25 17:29:51	753ms	2 NS 1 A 0 MX	🔓 Insecure
2026-06-23 14:37:14 shown	909ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-20 01:40:59	925ms	2 NS 1 A 0 MX	🔓 Insecure
2026-06-17 10:13:42	4161ms	2 NS 1 A 0 MX	🔓 Insecure