3mshop.dk

📜 Historical scan 2026-07-30 20:22:22 · ← Latest scan

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

3mshop.dk is a registered .dk domain whose nameservers (a.ns.3m.com, b.ns.3m.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 20 June 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#

2 records 59ms

Nameserver	IP addresses	PTR	ASN / ISP
a.ns.3m.com	162.159.8.174 2400:cb00:2049:1::a29f:8ae	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
b.ns.3m.com	173.245.58.19 2400:cb00:2049:1::adf5:3a13	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.

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

119ms

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-08 10:56:47

Field	Value
Registrar	CSC Digital Brand Service, Inc
Registered	2006-06-20
Expires	2027-06-30 (253d)

📋 WHOIS#

⏱️ Lookup Timing#

59ms

44ms

48ms

AAAA

42ms

TXT

259ms

CAA

45ms

HTTPS

40ms

TLSA

29ms

SOA

28ms

MTA-STS

61ms

DNSSEC

119ms

SRV

9545ms

Total

10138ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 22:39:51	1605ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-02 04:51:32	10430ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 08:26:37	1876ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 22:52:18	2887ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 12:16:37	1580ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 09:14:55	1453ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:06:16	3070ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:48:44	10630ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 07:30:10	1824ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:17:19	18047ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:33:55	3192ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:50:12	3762ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:47:59	16938ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 17:43:10	16633ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 18:19:36	3192ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 16:36:40	3892ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 06:51:24	16883ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 22:40:18	10273ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 02:36:37	2531ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 20:22:22 shown	10138ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 23:52:20	3287ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:15:12	3392ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:05:19	32931ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:39:25	16927ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:30:47	1940ms	2 NS 0 A 0 MX	❓ Unknown