bildung-rp.de

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns01.bildung-rp.de, ns02.bildung-rp.de. ns.bildung-rp.de, ns01.bildung-rp.de, ns02.bildung-rp.de, ns02.versatel.de, ns03.versatel.de report NS ns.bildung-rp.de ns01.bildung-rp.de ns02.bildung-rp.de ns02.versatel.de ns03.versatel.de.

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

SOA · The nameservers serve different versions of the zone: 2026100101 on ns02.bildung-rp.de (217.198.245.71); 2026101901 on ns.bildung-rp.de (217.198.244.11), ns01.bildung-rp.de (217.198.244.11), ns02.versatel.de (212.7.128.165), ns03.versatel.de (193.219.15.17). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

SOA · refresh 10m is outside 20m–1d; retry 2h should be shorter than refresh 10m. Current values: refresh 10m, retry 2h, expire 14d, negative TTL 10m.

DNSSEC · The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; 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.

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

MX · The following MX hosts could not be resolved to IPv6 addresses: mail.bildung-rp.de, mail02.bildung-rp.de, mail04.bildung-rp.de, mail05.bildung-rp.de

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

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

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.