boeckler.de

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns-ext.jmc-dns.de: "PowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:28:11 by root@localhost)"; ns-ext.jmc-dns.net: "PowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:28:11 by root@localhost)". Hide or replace the version string.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: mg.boeckler.de

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), s1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 213.202.248.10 (mg.boeckler.de). Ask your hosting provider to set one.

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.