SurfaceMap › t › thm.de

thm.de

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

Domain & DNS

warn

20 passed 3 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: dns1.fh-giessen.de: "9.18.49-1~deb12u2-Debian"; dns2.fh-giessen.de: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 30m, expire 14d, negative TTL 3d.
    #23
  • !
    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 thm.de ›

Mail

fail

19 passed 5 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
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    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
  • !
    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: mx.fh-giessen.de, mxb.fh-giessen.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

Recent checks

✗

Full report

Mail report for thm.de ›