Apex, subdomain, or URL. We figure it out.
Results for
metlife.com
Email authentication
The basics are in place but can be hardened.
- 3Pass
- 1Warning
- 0Fail
- 2Not set
SPF
WarningAuthorizes which servers may send mail for the domain
SPF is published but could be tightened.
- Policy
- ~all
- DNS lookups
- 8 / 10
- Ends in ~all (softfail): unauthorized senders are marked, not rejected.
- Uses 8 of 10 allowed DNS lookups. Close to the limit.
v=spf1 include:_spf.metlife.com include:_spf3.metlife.com ~allDKIM
PassCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 3 known selectors.
- Selectors
- default, smtp, mailjet
- Found a DKIM key at default._domainkey.metlife.com
- Found a DKIM key at smtp._domainkey.metlife.com
- Found a DKIM key at mailjet._domainkey.metlife.com
DMARC
PassTells receivers what to do with mail that fails SPF and DKIM
DMARC is enforced.
- Policy
- p=reject
- Coverage
- 100%
- Policy p=reject: failing mail is rejected outright.
- Aggregate reports (rua) are configured.
v=DMARC1;p=reject;rua=mailto:[email protected]MTA-STS
Not setEnforces TLS for inbound mail and prevents downgrade attacks
No MTA-STS policy. Inbound mail can be delivered without TLS.
TLS-RPT
Not setReceives reports about TLS delivery failures
No TLS-RPT record. You get no reports about failed TLS delivery.
BIMI
PassDisplays your verified brand logo in supporting inboxes
BIMI is published.
- Logo
- https://amplify.valimail.com/bimi/metlife/6jAoy6Dql8x-metropolitan_life_insurance_company_1375461757.svg
- VMC
- https://amplify.valimail.com/bimi/metlife/6jAoy6Dql8x-metropolitan_life_insurance_company_1375461757.pem
- A logo (l=) is published.
- A Verified Mark Certificate (a=) is referenced.
v=BIMI1; l=https://amplify.valimail.com/bimi/metlife/6jAoy6Dql8x-metropolitan_life_insurance_company_1375461757.svg; a=https://amplify.valimail.com/bimi/metlife/6jAoy6Dql8x-metropolitan_life_insurance_company_1375461757.pemChecks 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.