runnerz.dk

📜 Historical scan 2026-06-26 03:31:53  ·  ← Latest scan
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

runnerz.dk is a .dk domain served by 3 nameservers (helium.ns.hetzner.de, hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 88.198.201.76 is hosted by Hetzner Online GmbH (AS24940) in Germany. Mail is handled by fjellerad.beermann.dk. The zone is not DNSSEC-signed, has no DMARC policy and has no IPv6 address. 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   267ms

🌍 A Records#

1 records   261ms

📧 MX Records#

1 records   283ms

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

2 records   700ms
TXT Record
google-site-verification=hqmlMPQ7HqtM7Gp4D_G9K9teEdOQizTkiL94LOP87xE
v=spf1 a mx a:runnerz.dk ip4:88.198.201.76 ip4:88.198.201.76 ip6:fe80::9400:ff:fe3b:d7f0 ?all

✉️ SPF#

PolicyRecord (runnerz.dk)
?all (neutral) v=spf1 a mx a:runnerz.dk ip4:88.198.201.76 ip4:88.198.201.76 ip6:fe80::9400:ff:fe3b:d7f0 ?all

📨 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-10-11 16:21:07
www88.198.201.76 (AS24940) (address records, no CNAME)
www vs bare domainSame network
runnerz.dk: 88.198.201.76 (AS24940)
www.runnerz.dk: 88.198.201.76 (AS24940)
WildcardNo

✍️ DKIM keys#

1 found
SelectorCNAMEKey
default — RSA · ~2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

🔎 SPF check#

zone-wide SPF report

DNS lookups: 3/10 · policy: ?all

  • warn "?all" is neutral: it gives receivers no guidance, much like having no SPF

🔗 TLSA / DANE#

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

🔐 DNSSEC#

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

🏷️ SOA#

217ms
FieldValue
Serial2026061600
Primary NS (MNAME)ns1.first-ns.de
Responsible (RNAME)root@ns1.first-ns.de
Refresh10800s
Retry3600s
Expire604800s
Minimum (neg-cache TTL)38400s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup
📋 WHOIS#

⏱️ Lookup Timing#

NS
267ms
A
261ms
MX
283ms
AAAA
340ms
TXT
700ms
CAA
350ms
HTTPS
296ms
TLSA
262ms
SOA
217ms
MTA-STS
334ms
DNSSEC
514ms
SRV
365ms
Total
3307ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-24 13:30:31 883ms 3 NS 1 A 1 MX 🔓 Insecure
2026-09-01 03:36:22 9778ms 3 NS 1 A 1 MX 🔓 Insecure
2026-08-27 11:26:27 1073ms 3 NS 1 A 1 MX 🔓 Insecure
2026-06-26 03:31:53 shown 3307ms 3 NS 1 A 1 MX 🔓 Insecure
2026-06-22 21:04:08 1168ms 0 NS 0 A 0 MX ❓ Unknown
2026-06-17 11:37:38 1181ms 3 NS 1 A 1 MX 🔓 Insecure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone