SurfaceMap › p › ph-heidelberg.de

ph-heidelberg.de

Checked 2026-10-21 23:50 UTC · first added 2026-10-21
✗Problems found Score 72 of 100

Domain & DNS

warn

20 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: dns.uni-heidelberg.de: "9.11.36-RedHat-9.11.36-16.el8_10.16"; dns1.belwue.de: "PowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)"; dns2.uni-heidelberg.de: "9.11.36-RedHat-9.11.36-16.el8_10.16"; dns3.belwue.de: "PowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)"; dns5.belwue.de: "PowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)"; mta02.ph-heidelberg.de: "9.18.49-1~deb12u2-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 ph-heidelberg.de ›

Mail

fail

22 passed 4 warn 1 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: relay.uni-heidelberg.de, relay2.uni-heidelberg.de, relay3.uni-heidelberg.de
    #11
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc@exchange.uni-heidelberg.de (needs ph-heidelberg.de._report._dmarc.exchange.uni-heidelberg.de). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 ph-heidelberg.de ›