dmea.de

14 passed 6 warn 2 failed

Areas

Problems

• ✗

  No SPF record

  SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.

  #6
• ✗

  No DKIM keys published

  DKIM · _domainkey.dmea.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

  #7
• !

  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
• !

  Not enabled

  DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

  #8
• !

  Subdomains unprotected (sp=none)

  DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

  #20
• !

  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@Messe-Muenchen.de (needs dmea.de._report._dmarc.messe-muenchen.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
• !

  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 dmea.de ›