charlotdesign.dk

📜 Historical scan 2026-06-16 20:24:34 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

charlotdesign.dk is a .dk domain served by 2 nameservers (ns.dandomain.dk, ns2.dandomain.dk). It was registered on 26 April 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 185.221.38.141 is hosted by team.blue Denmark A/S (AS48854) in Denmark. The zone is DNSSEC-signed and validates, has no DMARC policy and has no IPv6 address. 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#

2 records 33ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.dandomain.dk	—	—	—
ns2.dandomain.dk	—	—	—

🌍 A Records#

1 records 31ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
185.221.38.141	—	s1c9lb2.shopfactory.io	AS48854	team.blue Denmark A/S	185.221.36.0/22	🇩🇰 Denmark	—

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

1 records 124ms

TXT Record
v=spf1 include:spf.dandomain.dk ?all

✉️ SPF#

Policy	Record (charlotdesign.dk)
?all (neutral)	v=spf1 include:spf.dandomain.dk ?all

📨 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-18 16:35:41

www	185.221.38.141 (AS48854) (address records, no CNAME)
www vs bare domain	Same network charlotdesign.dk: 185.221.38.141 (AS48854) www.charlotdesign.dk: 185.221.38.141 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEY	None 0 CDS, 0 CDNSKEY

🔎 SPF check#

zone-wide SPF report

DNS lookups: 3/10 · policy: ?all

warn "?all" is neutral: it gives receivers no guidance, much like having no SPF

🔗 TLSA / DANE#

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

🔐 DNSSEC#

73ms

Check	Result
Validation Status	🔒 Secure
AD Flag (resolver validates)	✓ Set
DS Record	✓ Found
DNSKEY Record	✓ Found
Flags	fully validated

🏷️ SOA#

65ms

Field	Value
Serial	2024042605
Primary NS (MNAME)	ns.dandomain.dk
Responsible (RNAME)	hostmaster@dandomain.dk
Refresh	14400s
Retry	3600s
Expire	1209600s
Minimum (neg-cache TTL)	300s

📋 Registration#

WHOIS fetched 2026-10-17 20:59:55

Field	Value
Registrar	DANDOMAIN A/S
Registered	2024-04-26
Expires	2027-04-25 (186d)

📋 WHOIS#

⏱️ Lookup Timing#

33ms

31ms

66ms

AAAA

76ms

TXT

124ms

CAA

45ms

HTTPS

80ms

TLSA

81ms

SOA

65ms

MTA-STS

61ms

DNSSEC

73ms

SRV

0ms

Total

337ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 10:13:25	317ms	2 NS 1 A 0 MX	🔒 Secure
2026-09-14 18:26:19	415ms	2 NS 1 A 0 MX	🔒 Secure
2026-07-02 01:00:00	480ms	2 NS 1 A 0 MX	🔒 Secure
2026-07-02 00:29:55	1594ms	2 NS 1 A 0 MX	🔒 Secure
2026-06-16 20:24:34 shown	337ms	2 NS 1 A 0 MX	🔒 Secure
2026-06-16 20:20:23	605ms	2 NS 1 A 0 MX	🔒 Secure