SurfaceMap › u › uni-speyer.de

uni-speyer.de

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

Domain & DNS

warn

22 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns-auth.rptu.de: "9.20.29-1~deb13u1-Debian"; srvbrei.dhv-speyer.de: "9.16.23-RH"; srvrei.dhv-speyer.de: "9.16.23-RH"; xlink1.xlink.net: "9.9.5-9+deb8u19-Debian". Hide or replace the version string.
    #17
  • !
    Not signed
    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.
    #27

Recent checks

!

Full report

Domain & DNS report for uni-speyer.de ›

Mail

fail

21 passed 2 warn 2 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✗
    No DKIM keys published
    DKIM · _domainkey.uni-speyer.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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 uni-speyer.de ›