bayern-online.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: ns3.nsentry.de: "PowerDNS Authoritative Server 5.1.4 (built Aug 5 2026 13:21:12 by root@localhost)"; ns4.nsentry.de: "PowerDNS Authoritative Server 4.8.5 (built Feb 7 2025 09:28:41 by root@localhost)". Hide or replace the version string.

SOA · negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 1000h, negative TTL 2d.

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.

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: mx.zoho.eu, mx2.zoho.eu, mx3.zoho.eu

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

MX · The PTR name of these addresses does not resolve back to the same address: 185.230.214.166 -> mx3.zoho.eu.

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.