SurfaceMap › h › hs-mainz.de

hs-mainz.de

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

Domain & DNS

fail

21 passed 2 warn 2 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: barrow.hs-mainz.de (143.93.114.99): read udp 46.225.38.91:54529->143.93.114.99:53: i/o timeout.
    #14
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns.hs-worms.de (143.93.160.9): read tcp 46.225.38.91:57854->143.93.160.9:53: i/o timeout.
    #19
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.hs-worms.de: "9.20.30". 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 hs-mainz.de ›

Mail

fail

14 passed 4 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.hs-mainz.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
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: mailgate-4.zdv.net
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mailgate-4.zdv.net
    #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

Recent checks

✗

Full report

Mail report for hs-mainz.de ›