hartzpickles.dk

📜 Historical scan 2026-07-28 20:38:21 · ← Latest scan

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

hartzpickles.dk is a registered .dk domain whose nameservers (ns1.ascio.net, ns2.ascio.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 21 August 2001 (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 604ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.ascio.net	156.154.130.100 2610:a1:1022::100	ns.domainnetwork.se ns2.domainnetwork.se	AS12008 Vercara, LLC AS12008 Vercara, LLC
ns2.ascio.net	156.154.131.100 2610:a1:1023::100	ns2.netnames.net pdns2.cscdns.net	AS12008 Vercara, LLC AS12008 Vercara, LLC

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

650ms

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-21 23:14:17

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-08-21
Expires	2027-09-30 (343d)

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

604ms

603ms

584ms

AAAA

581ms

TXT

1994ms

CAA

572ms

HTTPS

576ms

TLSA

342ms

SOA

183ms

MTA-STS

595ms

DNSSEC

650ms

SRV

580ms

Total

3733ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-21 23:29:14	4242ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 16:52:36	2514ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 18:21:57	10872ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:36:07	4403ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:49:32	6127ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:37:02	6551ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:27:05	2287ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 15:31:32	16988ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 15:26:40	2858ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:44:35	11002ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 05:59:49	4633ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 16:51:11	3453ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 11:29:16	3600ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 06:41:39	5218ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 00:38:31	2808ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 21:27:21	4690ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 20:38:21 shown	3733ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:32:23	1258ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:19:41	2857ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:53:39	16827ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:08:48	2965ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:51:14	1241ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 14:19:37	2689ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 13:45:03	1122ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:16:23	10913ms	2 NS 0 A 0 MX	❓ Unknown