ewear.dk

📜 Historical scan 2026-06-23 04:08:13 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

ewear.dk is a .dk domain with no delegation in this scan. It was registered on 3 June 2025 (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-19 20:19:49

www CNAME	shops.myshopify.com (all on myshopify.com) → 23.227.38.74 2620:127:f00f:e:: (AS13335)
www vs bare domain	Same network ewear.dk: 23.227.38.65 (AS13335) www.ewear.dk: 23.227.38.74 2620:127:f00f:e:: (AS13335)
Wildcard	No

🔗 TLSA / DANE#

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

🔐 DNSSEC#

480ms

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-18 19:46:02

Field	Value
Registrar	Realtime Register B.V.
Registered	2025-06-03
Expires	2027-06-02 (222d)

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

175ms

189ms

195ms

AAAA

185ms

TXT

517ms

CAA

203ms

HTTPS

198ms

TLSA

17ms

SOA

174ms

MTA-STS

195ms

DNSSEC

480ms

SRV

217ms

Total

1181ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-19 20:19:49	798ms	2 NS 1 A 0 MX	🔓 Insecure
2026-10-18 19:34:19	1332ms	2 NS 1 A 0 MX	🔓 Insecure
2026-10-15 09:09:49	854ms	2 NS 1 A 0 MX	🔓 Insecure
2026-10-08 22:46:59	943ms	2 NS 1 A 0 MX	🔓 Insecure
2026-10-01 19:00:22	712ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-24 17:38:40	1884ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-21 01:49:23	1042ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-14 00:58:14	1057ms	2 NS 1 A 0 MX	🔓 Insecure
2026-09-04 08:13:39	632ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-27 14:19:02	654ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-20 15:31:43	2530ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-13 13:53:31	2049ms	2 NS 1 A 0 MX	🔓 Insecure
2026-08-08 02:09:14	1093ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-30 06:03:13	16874ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:44:23	711ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-17 10:54:03	762ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-14 06:03:49	732ms	2 NS 1 A 0 MX	🔓 Insecure
2026-07-03 12:16:16	1675ms	2 NS 1 A 0 MX	🔓 Insecure
2026-06-25 18:54:20	2334ms	2 NS 1 A 0 MX	🔓 Insecure
2026-06-23 04:08:13 shown	1181ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-21 06:30:08	942ms	2 NS 1 A 0 MX	🔓 Insecure
2026-06-17 09:08:31	926ms	2 NS 1 A 0 MX	🔓 Insecure