shop4feet.dk

📜 Historical scan 2026-08-10 22:18:55 · ← Latest scan

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

shop4feet.dk is a registered .dk domain whose nameservers (ns1.bellcom.dk, ns2.bellcom.dk, ns3.bellcom.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 29 March 2008 (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#

3 records 569ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.bellcom.dk	49.12.97.194	static.194.97.12.49.clients.your-server.de	AS24940 Hetzner Online GmbH
ns2.bellcom.dk	95.216.143.227	static.227.143.216.95.clients.your-server.de	AS24940 Hetzner Online GmbH
ns3.bellcom.dk	5.75.170.80	static.80.170.75.5.clients.your-server.de	AS24940 Hetzner Online GmbH

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

9575ms

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-24 23:02:14

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-03-29
Expires	2027-03-31 (155d)

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

569ms

565ms

550ms

AAAA

566ms

TXT

2809ms

CAA

604ms

HTTPS

585ms

TLSA

553ms

SOA

43ms

MTA-STS

602ms

DNSSEC

9575ms

SRV

645ms

Total

12407ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-08 14:19:56	12484ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:12:48	8396ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:03:09	2750ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:00:00	4093ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:12:06	2394ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:55:27	2811ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 13:40:43	7311ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:29:13	6659ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 15:36:29	6424ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 10:07:10	5115ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 22:18:55 shown	12407ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 20:20:03	18401ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 10:08:58	12665ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 19:23:36	5900ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 12:26:40	4865ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 16:07:32	14263ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:29:00	2643ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:54:19	2702ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:29:04	5661ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:14:12	9673ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 10:25:15	5044ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:12:17	1944ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 03:06:01	12402ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 02:33:45	3324ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-16 20:37:27	3214ms	3 NS 0 A 0 MX	❓ Unknown