hamburg.de

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2.mcs.de: "PowerDNS Authoritative Server 4.8.3"; ns3.mcs.de: "PowerDNS Authoritative Server 4.8.3". Hide or replace the version string.

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

MX · The following MX hosts could not be resolved to IPv6 addresses: mailin.hamburg.de, secondary.snafu.de

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: s2 (1024 bits). Rotate to a 2048-bit key.

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarcreport@team.snafu.de (needs hamburg.de._report._dmarc.team.snafu.de). Ask the report provider to publish the record, or check the address.

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 84.23.254.17 (secondary.snafu.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.