n24.de

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-130.akam.net: "41824.10"; a11-67.akam.net: "41824.5"; a11-67.akam.net: "41824.8"; a14-64.akam.net: "48878.32"; a14-64.akam.net: "48878.27"; a16-65.akam.net: "48878.29"; a16-65.akam.net: "48878.27"; a6-66.akam.net: "48878.27"; a7-67.akam.net: "41824.6"; a7-67.akam.net: "41824.4". 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.

SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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

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

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

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

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.