wdr5.de

SOA · The nameservers serve different versions of the zone: 313 on dnsext03.wdr.de (149.219.215.11); 329 on dnsext02.wdr.de (149.219.215.10), pdns02.domaincontrol.com (173.201.78.50), pdns02.domaincontrol.com (2603:5:22e0::32). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

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.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 5m; resolvers may use either.

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 · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

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.