Apex, subdomain, or URL. We figure it out.
Results for
bp.com
Email authentication
The basics are in place but can be hardened.
- 3Pass
- 2Warning
- 0Fail
- 1Not set
SPF
WarningAuthorizes which servers may send mail for the domain
SPF is published but could be tightened.
- Policy
- -all
- DNS lookups
- 10 / 10
- Ends in -all (hardfail): unauthorized senders are rejected.
- Uses 10 of 10 allowed DNS lookups. Close to the limit.
v=spf1 include:_u.bp.com._spf.smart.ondmarc.com -allDKIM
PassCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 7 known selectors.
- Selectors
- selector1, selector2, s1, s2, mandrill, mailjet, mte1
- Found a DKIM key at selector1._domainkey.bp.com
- Found a DKIM key at selector2._domainkey.bp.com
- Found a DKIM key at s1._domainkey.bp.com
- Found a DKIM key at s2._domainkey.bp.com
- Found a DKIM key at mandrill._domainkey.bp.com
- Found a DKIM key at mailjet._domainkey.bp.com
- Found a DKIM key at mte1._domainkey.bp.com
DMARC
PassTells receivers what to do with mail that fails SPF and DKIM
DMARC is enforced.
- Policy
- p=reject
- Subdomains
- sp=reject
- Coverage
- 100%
- Policy p=reject: failing mail is rejected outright.
- Aggregate reports (rua) are configured.
v=DMARC1; p=reject; pct=100; sp=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; adkim=r; aspf=r; fo=1; rf=afrf; ri=3600MTA-STS
WarningEnforces TLS for inbound mail and prevents downgrade attacks
MTA-STS is published but not enforcing.
- Mode
- testing
- Max age
- 86401s
- Policy mode is testing: failures are reported but mail is still delivered.
v=STSv1; id=1777305807037TLS-RPT
PassReceives reports about TLS delivery failures
TLS reporting is configured.
- Reports to
- mailto:[email protected]
- TLS delivery failure reports are being collected.
v=TLSRPTv1; rua=mailto:[email protected];BIMI
Not setDisplays your verified brand logo in supporting inboxes
No BIMI record. No brand logo is published for inboxes.
Checks query live DNS over Cloudflare and the public MTA-STS policy endpoint. DKIM selectors cannot be listed from DNS, so DKIM detection probes common provider selectors only.