SurfaceMap › b › brandenburg.de

brandenburg.de

Checked 2026-10-21 21:54 UTC · first added 2026-10-21
✗Problems found Score 68 of 100

Domain & DNS

warn

27 passed 1 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC ✓Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.brandenburg.de: "Public DNS server v28.3.2. Keep your hands off!"; pns.brandenburg.de: "Public DNS server v28.3.2. Keep your hands off!". Hide or replace the version string.
    #17

Recent checks

!

Full report

Domain & DNS report for brandenburg.de ›

Mail

fail

19 passed 3 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.brandenburg.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: pmmx-hea-p01.brandenburg.de, pmmx-hea-p02.brandenburg.de
    #11
  • !
    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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for brandenburg.de ›