sitejabber.com

22 passed 8 warn 1 failed

Areas

Problems

• ✗

  DMARC not strict enough for BIMI

  BIMI · Mail clients will not show the logo. BIMI requires a subdomain policy other than sp=none.

  #39
• !

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

  More than 5 MX records

  MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

  #13
• !

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

  1024-bit DKIM key

  DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits), google (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.

  #23
• !

  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:tech.evgenii@gmail.com (needs sitejabber.com._report._dmarc.gmail.com). 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
• !

  No certificate (a=)

  BIMI · The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

  #38

Recent checks

Full report

Mail report for sitejabber.com ›