chr-bo.dk

📜 Historical scan 2026-06-25 18:27:48  ·  ← Latest scan
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

chr-bo.dk is a .dk domain served by 3 nameservers (ns.second-ns.com, ns1.your-server.de, ns3.second-ns.de). It was registered on 22 February 2007 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 78.46.9.38 is hosted by Hetzner Online GmbH (AS24940) in Germany. Mail is handled by aspmx.l.google.com, alt1.aspmx.l.google.com and 3 more. 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   47ms

🌍 A Records#

1 records   158ms

📧 MX Records#

5 records   43ms

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

🔌 SRV Records#

1 records   201ms
ServicePriorityWeightPortTarget
_autodiscover._tcp 0 100 443 mail.your-server.de

📝 TXT Records#

2 records   251ms
TXT Record
google-site-verification=ttJV9LVNHKSRUlRTszeOQzMoXUY0FIXqImLFINCiSmA
v=spf1 +a +mx ?all

✉️ SPF#

PolicyRecord (chr-bo.dk)
?all (neutral) v=spf1 +a +mx ?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-10 06:42:05
www78.46.9.38 (AS24940) (address records, no CNAME)
www vs bare domainSame network
chr-bo.dk: 78.46.9.38 (AS24940)
www.chr-bo.dk: 78.46.9.38 (AS24940)
WildcardNo

✍️ DKIM keys#

1 found
SelectorCNAMEKey
google — 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: 2/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#

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

🏷️ SOA#

95ms
FieldValue
Serial2025121100
Primary NS (MNAME)ns1.your-server.de
Responsible (RNAME)postmaster@your-server.de
Refresh86400s
Retry10800s
Expire3600000s
Minimum (neg-cache TTL)7200s

📋 Registration#

WHOIS fetched 2026-10-10 10:45:06
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2007-02-22
Expires2027-02-28 (129d)
📋 WHOIS#

⏱️ Lookup Timing#

NS
47ms
A
158ms
MX
43ms
AAAA
105ms
TXT
251ms
CAA
77ms
HTTPS
77ms
TLSA
49ms
SOA
95ms
MTA-STS
82ms
DNSSEC
126ms
SRV
201ms
Total
851ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-08-15 19:09:26 1255ms 3 NS 1 A 1 MX 🔓 Insecure
2026-06-26 01:42:04 2294ms 3 NS 1 A 5 MX 🔓 Insecure
2026-06-25 18:27:48 shown 851ms 3 NS 1 A 5 MX 🔓 Insecure
2026-06-25 02:49:16 2961ms 3 NS 1 A 5 MX ❓ Unknown
2026-06-20 02:21:27 687ms 3 NS 1 A 5 MX 🔓 Insecure
2026-06-16 20:35:14 764ms 3 NS 1 A 5 MX 🔓 Insecure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone