chase.com

Live email deliverability and anti-spoofing audit. Every value below was read from public DNS at the moment this page was generated.

Findings

• dkim

  No DKIM key found at any common selector. Either DKIM is not configured, or it uses a custom selector we cannot discover from DNS alone.

  Fix: Enable DKIM signing at your mail provider and publish the selector they give you.

• mta sts

  No MTA-STS policy, so inbound mail can be downgraded to an unencrypted connection.

  Fix: Publish _mta-sts.chase.com and host a policy at https://mta-sts.chase.com/.well-known/mta-sts.txt.

• mx

  4 mail exchangers published.

  10 cluster14.us.messagelabs.com, 20 cluster14.us.messagelabs.com, 30 cluster14.us.messagelabs.com, 40 cluster14a.us.messagelabs.com

• spf

  SPF is published and enforcing.

  v=spf1 include:tpo.chase.com exists:%{i}.spf.chase.com exists:%{i}.spf.hc4673-96.iphmx.com exists:%{i}.spf.hc4698-8.iphmx.com -all

• dmarc

  DMARC is enforcing with p=reject.

  v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;

• bimi

  BIMI is published; supporting clients can show your logo.

  v=BIMI1;l=https://vmc.digicert.com/56fc8a64-c1ec-48b1-9f70-ae068ebbe8d0.svg;a=https://vmc.digicert.com/56fc8a64-c1ec-48b1-9f70-ae068ebbe8d0.pem

Records

curl "https://mailgrade.dev/v1/domain?domain=chase.com"

Check another domain