metlife.fr

Checked 22 October 2026, 04:20 UTC · via 8.8.8.8
!Passed with warnings
25 passed 4 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.metlife.com include:spf.mailjet.com -all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.metlife.fr)

Found

Record
v=DMARC1;p=reject;rua=mailto:dmarc_agg@vali.email
Found at
_dmarc.metlife.fr
External report address
mailto:dmarc_agg@vali.email (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:dmarc_agg@vali.emailAggregate report addresses

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_agg@vali.email
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.metlife.comA 139.138.56.187 A 139.138.56.198 A 216.71.155.56 A 139.138.33.12 A 216.71.155.54 A 216.71.155.64 A 139.138.33.23 A 139.138.56.189 A 68.232.157.141 A 139.138.33.15 A 68.232.157.134 A 216.71.155.62 A 139.138.56.199 A 139.138.56.188 A 139.138.33.11 A 139.138.33.24 A 139.138.56.184 A 68.232.157.163 A 68.232.157.126 A 139.138.33.13esa11.hc1983-11.iphmx.com ✓ esa17.hc1983-11.iphmx.com ✓ esa5.hc1983-11.iphmx.com ✓ esa12.hc1983-11.iphmx.com ✓ esa4.hc1983-11.iphmx.com ✓ esa8.hc1983-11.iphmx.com ✓ esa18.hc1983-11.iphmx.com ✓ esa15.hc1983-11.iphmx.com ✓ esa3.hc1983-11.iphmx.com ✓ esa16.hc1983-11.iphmx.com ✓ esa2.hc1983-11.iphmx.com ✓ esa6.hc1983-11.iphmx.com ✓ esa19.hc1983-11.iphmx.com ✓ esa13.hc1983-11.iphmx.com ✓ esa10.hc1983-11.iphmx.com ✓ esa20.hc1983-11.iphmx.com ✓ esa9.hc1983-11.iphmx.com ✓ esa7.hc1983-11.iphmx.com ✓ esa1.hc1983-11.iphmx.com ✓ esa14.hc1983-11.iphmx.com ✓
10mx2.metlife.comA 139.138.33.23 A 216.71.155.56 A 139.138.56.199 A 139.138.33.11 A 68.232.157.141 A 139.138.56.198 A 68.232.157.134 A 139.138.56.189 A 68.232.157.126 A 68.232.157.163 A 216.71.155.54 A 139.138.33.24 A 216.71.155.62 A 139.138.56.184 A 216.71.155.64 A 139.138.33.13 A 139.138.33.12 A 139.138.56.188 A 139.138.56.187 A 139.138.33.15esa18.hc1983-11.iphmx.com ✓ esa5.hc1983-11.iphmx.com ✓ esa19.hc1983-11.iphmx.com ✓ esa10.hc1983-11.iphmx.com ✓ esa3.hc1983-11.iphmx.com ✓ esa17.hc1983-11.iphmx.com ✓ esa2.hc1983-11.iphmx.com ✓ esa15.hc1983-11.iphmx.com ✓ esa1.hc1983-11.iphmx.com ✓ esa7.hc1983-11.iphmx.com ✓ esa4.hc1983-11.iphmx.com ✓ esa20.hc1983-11.iphmx.com ✓ esa6.hc1983-11.iphmx.com ✓ esa9.hc1983-11.iphmx.com ✓ esa8.hc1983-11.iphmx.com ✓ esa14.hc1983-11.iphmx.com ✓ esa12.hc1983-11.iphmx.com ✓ esa13.hc1983-11.iphmx.com ✓ esa11.hc1983-11.iphmx.com ✓ esa16.hc1983-11.iphmx.com ✓
100mx1.hc1983-11.iphmx.comA 68.232.157.134 A 68.232.157.163 A 139.138.56.199 A 139.138.56.188 A 139.138.56.184 A 139.138.56.198 A 139.138.56.187 A 139.138.33.24 A 68.232.157.141 A 68.232.157.126 A 139.138.33.12 A 139.138.33.15 A 139.138.33.11 A 216.71.155.54 A 216.71.155.56 A 139.138.33.13 A 216.71.155.64 A 139.138.56.189 A 216.71.155.62 A 139.138.33.23esa2.hc1983-11.iphmx.com ✓ esa7.hc1983-11.iphmx.com ✓ esa19.hc1983-11.iphmx.com ✓ esa13.hc1983-11.iphmx.com ✓ esa9.hc1983-11.iphmx.com ✓ esa17.hc1983-11.iphmx.com ✓ esa11.hc1983-11.iphmx.com ✓ esa20.hc1983-11.iphmx.com ✓ esa3.hc1983-11.iphmx.com ✓ esa1.hc1983-11.iphmx.com ✓ esa12.hc1983-11.iphmx.com ✓ esa16.hc1983-11.iphmx.com ✓ esa10.hc1983-11.iphmx.com ✓ esa4.hc1983-11.iphmx.com ✓ esa5.hc1983-11.iphmx.com ✓ esa14.hc1983-11.iphmx.com ✓ esa8.hc1983-11.iphmx.com ✓ esa15.hc1983-11.iphmx.com ✓ esa6.hc1983-11.iphmx.com ✓ esa18.hc1983-11.iphmx.com ✓
100mx2.hc1983-11.iphmx.comA 139.138.56.184 A 68.232.157.134 A 139.138.33.15 A 216.71.155.62 A 139.138.33.12 A 139.138.33.13 A 139.138.33.23 A 139.138.56.188 A 68.232.157.163 A 139.138.56.187 A 139.138.56.198 A 216.71.155.64 A 68.232.157.141 A 139.138.33.24 A 68.232.157.126 A 139.138.33.11 A 139.138.56.199 A 216.71.155.56 A 216.71.155.54 A 139.138.56.189esa9.hc1983-11.iphmx.com ✓ esa2.hc1983-11.iphmx.com ✓ esa16.hc1983-11.iphmx.com ✓ esa6.hc1983-11.iphmx.com ✓ esa12.hc1983-11.iphmx.com ✓ esa14.hc1983-11.iphmx.com ✓ esa18.hc1983-11.iphmx.com ✓ esa13.hc1983-11.iphmx.com ✓ esa7.hc1983-11.iphmx.com ✓ esa11.hc1983-11.iphmx.com ✓ esa17.hc1983-11.iphmx.com ✓ esa8.hc1983-11.iphmx.com ✓ esa3.hc1983-11.iphmx.com ✓ esa20.hc1983-11.iphmx.com ✓ esa1.hc1983-11.iphmx.com ✓ esa10.hc1983-11.iphmx.com ✓ esa19.hc1983-11.iphmx.com ✓ esa5.hc1983-11.iphmx.com ✓ esa4.hc1983-11.iphmx.com ✓ esa15.hc1983-11.iphmx.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx1.metlife.com, mx2.metlife.com, mx1.hc1983-11.iphmx.com, mx2.hc1983-11.iphmx.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 80 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.metlife.comnone-
mx2.metlife.comnone-
mx1.hc1983-11.iphmx.comnone-
mx2.hc1983-11.iphmx.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

pass

https://amplify.valimail.com/bimi/metlife/e2pSWKZot9x-MetLife_New.svg

Found

Record
v=BIMI1; l=https://amplify.valimail.com/bimi/metlife/e2pSWKZot9x-MetLife_New.svg; a=https://amplify.valimail.com/bimi/metlife/e2pSWKZot9x-MetLife_New.pem
Found at
default._bimi.metlife.fr
Logo
https://amplify.valimail.com/bimi/metlife/e2pSWKZot9x-MetLife_New.svg
Certificate
https://amplify.valimail.com/bimi/metlife/e2pSWKZot9x-MetLife_New.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://amplify.valimail.com/bimi/metlife/e2pSWKZot9x-MetLife_New.svg; certificate: https://amplify.valimail.com/bimi/metlife/e2pSWKZot9x-MetLife_New.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.