detail.de

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: annabel.ns.cloudflare.com: "2026.10.2"; arch.ns.cloudflare.com: "2026.10.2". 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.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (42s), AAAA (1m). Low TTLs are useful just before a planned change.

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.

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (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:noreply@snk.de (needs detail.de._report._dmarc.snk.de). Ask the report provider to publish the record, or check the address.

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.