SurfaceMap › r › rheinbahn.de

rheinbahn.de

Checked 2026-10-22 00:00 UTC · first added 2026-10-21
✗Problems found Score 60 of 100

Domain & DNS

fail

19 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns.rheinbahn.de (194.31.227.34): 470 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 194.31.227.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Unusual SOA timers
    SOA · refresh 7d is outside 20m–1d; negative caching TTL (minimum) 7d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 7d, retry 1d, expire 28d, negative TTL 7d.
    #23
  • !
    Signed but not delegated securely
    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.
    #27

Recent checks

✗

Full report

Domain & DNS report for rheinbahn.de ›

Mail

warn

22 passed 6 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Signed, but no DS at parent
    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.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.rheinbahn.de, mx2.rheinbahn.de
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    Not configured
    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.
    #32

Recent checks

!

Full report

Mail report for rheinbahn.de ›