metro.fr

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

SPF

info

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com include:spf.ymag.cloud include:_spf.metro.fr a:pccmail2.atgpedi.net a:pccmail1.atgpedi.net ip4:109.69.194.163 exists:%{i}.spf.hc2116-98.eu.iphmx.com redirect=spf.metro.info
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 9 of 10 DNS lookups #2
    SPF record needs 9 DNS lookups (limit is 10).
  • i
    Delegated via redirect
    SPF record has no 'all' mechanism but redirects to spf.metro.info, whose policy applies.
    #3
  • ✓ 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.metro.fr)

Found

Record
v=DMARC1; p=reject; rua=mailto:4e4w5tjg5g@rua.powerdmarc.com,mailto:dmarc-rua@metro.digital;
Found at
_dmarc.metro.fr
External report address
mailto:4e4w5tjg5g@rua.powerdmarc.com (authorized)
External report address
mailto:dmarc-rua@metro.digital (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:4e4w5tjg5g@rua.powerdmarc.com,mailto:dmarc-rua@metro.digitalAggregate 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:4e4w5tjg5g@rua.powerdmarc.com, mailto:dmarc-rua@metro.digital
  • ✓ 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

pass

Selectors: selector1, s1

Found

Selectors
selector1, s1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
s1RSA 2048 bits

Checks

  • ✓ Keys found: selector1, s1 #7
    DKIM keys found for this domain with selectors: selector1, s1
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; s1: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.hc611-36.eu.iphmx.comA 23.90.104.169 A 207.54.77.186esa.hc611-36.eu.iphmx.com ✓ esa.hc611-36.eu.iphmx.com ✓
10mx2.hc611-36.eu.iphmx.comA 23.90.104.169 A 207.54.77.186esa.hc611-36.eu.iphmx.com ✓ esa.hc611-36.eu.iphmx.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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.hc611-36.eu.iphmx.com, mx2.hc611-36.eu.iphmx.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.hc611-36.eu.iphmx.comnone-
mx2.hc611-36.eu.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

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38