shophumanoid.dk

📜 Historical scan 2026-07-08 11:11:14 · ← Latest scan

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

shophumanoid.dk is a registered .dk domain whose nameservers (ns.eatserver.nl, ns2.eatserver.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 28 January 2016 (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 183ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.eatserver.nl	2001:1460:3:4:1c00:aeff:fe00:2715 62.221.202.210	ns.eatserver.nl ns.eatserver.nl	AS48635 Your Hosting B.V. AS48635 Your Hosting B.V.
ns2.eatserver.nl	195.20.11.100 2001:1460:2:0:1c21:e9ff:fe00:1b6	ns2.eatserver.nl ns2.eatserver.nl	AS48635 Your Hosting B.V. AS48635 Your Hosting B.V.

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

1194ms

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-25 02:11:45

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2016-01-28
Expires	2027-01-31 (98d)

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

183ms

79ms

1170ms

AAAA

853ms

TXT

9676ms

CAA

96ms

HTTPS

84ms

TLSA

167ms

SOA

49ms

MTA-STS

1825ms

DNSSEC

1194ms

SRV

647ms

Total

11603ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 09:59:49	20660ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 03:06:05	23627ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 05:00:45	20101ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:34:14	21565ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:09:41	11382ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:01:57	4921ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:35:07	12395ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 18:54:15	20629ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:23:47	2360ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 13:54:43	19311ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 10:59:26	19069ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:05:02	12721ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:25:16	18303ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 23:27:43	9750ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 02:31:22	18743ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:46:08	23622ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:10:41	25758ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:26:39	17906ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:22:30	11670ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:22:29	3670ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 23:35:20	18073ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 21:09:38	3998ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 17:33:30	20699ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 07:43:12	3886ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 07:28:56	8398ms	2 NS 0 A 0 MX	❓ Unknown