SurfaceMap › h › hs-mittweida.de

hs-mittweida.de

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

Domain & DNS

fail

20 passed 2 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns.hs-mittweida.de (2001:638:91c:3000::32): read udp [2a01:4f8:1c1c:eebf::1]:51728->[2001:638:91c:3000::32]:53: i/o timeout; dns2.hs-mittweida.de (2001:638:91c:3000::33): read udp [2a01:4f8:1c1c:eebf::1]:60000->[2001:638:91c:3000::33]:53: i/o timeout.
    #14
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: dns.hs-mittweida.de (glue 141.55.192.50, zone 141.55.192.50, 2001:638:91c:3000::32); dns2.hs-mittweida.de (glue 141.55.192.51, zone 141.55.192.51, 2001:638:91c:3000::33). Update the glue at your registrar.
    #8
  • !
    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-mittweida.de ›

Mail

fail

23 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
  • !
    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: a1021.mx.srv.dfn.de, b1021.mx.srv.dfn.de, c1021.mx.srv.dfn.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 hs-mittweida.de ›