analytica.de

21 passed 8 warn 0 failed

Areas

Problems

• !

  Ends with ?all (neutral)

  SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

  #3
• !

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

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