SurfaceMap › b › bagso.de

bagso.de

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

Domain & DNS

fail

21 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    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: ns1.st-nameserver.de (51.195.22.9): dial tcp 51.195.22.9:53: connect: connection refused; ns2.st-dns.de (51.75.151.198): dial tcp 51.75.151.198:53: connect: connection refused; ns3.st-dns.net (185.117.182.99): dial tcp 185.117.182.99:53: connect: connection refused.
    #19
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.st-nameserver.de (51.195.22.9), ns2.st-dns.de (51.75.151.198), ns3.st-dns.net (185.117.182.99).
    #20
  • !
    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 bagso.de ›

Mail

fail

21 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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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 bagso.de ›