SurfaceMap › h › hs-bremen.de

hs-bremen.de

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

Domain & DNS

fail

21 passed 3 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: dns1.belwue.de (129.143.2.10): REFUSED, authoritative=false; dns1.belwue.de (2001:7c0::53:10): REFUSED, authoritative=false.
    #15
  • ✗
    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: dns1.belwue.de (129.143.2.10): ; dns1.belwue.de (2001:7c0::53:10): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.belwue.de. dns-2.dfn.de, dns.hs-bremen.de, dns2.hs-bremen.de report NS dns-2.dfn.de dns.hs-bremen.de dns2.hs-bremen.de.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns.hs-bremen.de: "9.18.49-1~deb12u2-Debian"; dns1.belwue.de: "PowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)"; dns2.hs-bremen.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 hs-bremen.de ›

Mail

fail

20 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
  • !
    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
  • !
    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-bremen.de ›