SurfaceMap › a › aufstiegs-bafoeg.de

aufstiegs-bafoeg.de

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

Domain & DNS

warn

23 passed 1 warn 0 failed

Areas

iRegistration iDelegation iNameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    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 aufstiegs-bafoeg.de ›

Mail

fail

21 passed 7 warn 1 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX ✗TLS iBIMI

Problems

  • ✗
    TLSA records not DNSSEC-validated
    TLS · These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: r2mr5.init.de.
    #36
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: r2mr5.init.de
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports-rua@init.de (needs aufstiegs-bafoeg.de._report._dmarc.init.de); mailto:dmarc-reports-ruf@init.de (needs aufstiegs-bafoeg.de._report._dmarc.init.de). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 aufstiegs-bafoeg.de ›