heartlabs.dk

Historical scan 2026-09-24 20:41:12  ·  ← Latest scan
Zone File Timeline & History Scan Now

heartlabs.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 15 December 2025 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is not DNSSEC-signed, has no DMARC policy and is reachable over IPv6. 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   71ms

A Records#

2 records   65ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.168 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.176 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   59ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:eb0b:8ae9:3013:6add:16c5 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:5fa1:e1a8:b5b0:f302:d310 60s — AS47583 — — 🇨🇾 Cyprus —

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-11-13 00:06:44

TLSA / DANE#

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

DNSSEC#

169ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsunsigned answer

SOA#

0ms
FieldValue
Serial2026092401
Primary NS (MNAME)ns1.dns-parking.com
Responsible (RNAME)dns@hostinger.com
Refresh10000s
Retry2400s
Expire604800s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-10-30 06:33:16
FieldValue
RegistrarRealtime Register B.V.
Registered2025-12-15
Expires2026-12-14 (26d)

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#

NS
71ms
A
65ms
MX
69ms
AAAA
59ms
TXT
380ms
CAA
56ms
HTTPS
56ms
TLSA
97ms
SOA
0ms
MTA-STS
101ms
DNSSEC
169ms
SRV
257ms
Total
927ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-13 00:06:44 738ms 2 NS 2 A 0 MX Insecure
2026-11-05 21:32:17 901ms 2 NS 2 A 0 MX Insecure
2026-10-30 06:15:02 717ms 2 NS 2 A 0 MX Insecure
2026-10-22 13:44:44 714ms 2 NS 2 A 0 MX Insecure
2026-10-15 05:20:41 666ms 2 NS 2 A 0 MX Insecure
2026-10-08 12:56:49 2228ms 2 NS 2 A 0 MX Insecure
2026-10-01 11:31:12 1018ms 2 NS 2 A 0 MX Insecure
2026-09-26 11:00:33 863ms 2 NS 2 A 0 MX Insecure
2026-09-24 20:41:12 shown 927ms 2 NS 2 A 0 MX Insecure
2026-09-23 20:10:36 928ms 2 NS 2 A 0 MX Insecure
2026-09-12 13:54:38 1263ms 2 NS 2 A 0 MX Insecure
2026-09-08 17:39:42 1009ms 2 NS 2 A 0 MX Insecure
2026-09-04 10:44:16 720ms 2 NS 2 A 0 MX Insecure
2026-09-01 06:36:29 1030ms 2 NS 2 A 0 MX Insecure
2026-08-27 20:21:34 880ms 2 NS 2 A 0 MX Insecure
2026-08-26 20:01:44 2672ms 2 NS 2 A 0 MX Insecure
2026-08-25 11:22:13 719ms 2 NS 2 A 0 MX Insecure
2026-08-21 01:31:51 8581ms 2 NS 2 A 0 MX Unknown
2026-08-13 16:57:00 1980ms 2 NS 2 A 0 MX Insecure
2026-08-08 18:08:44 1951ms 2 NS 2 A 0 MX Insecure
2026-07-31 14:37:53 912ms 2 NS 2 A 0 MX Insecure
2026-07-23 06:49:40 8899ms 2 NS 2 A 0 MX Insecure
2026-07-16 12:09:53 958ms 2 NS 2 A 0 MX Insecure
2026-07-11 18:24:40 8859ms 2 NS 2 A 0 MX Insecure
2026-07-03 17:33:41 1107ms 2 NS 2 A 0 MX Insecure