reims.fr

Checked 22 October 2026, 05:00 UTC · via 8.8.8.8
✗Problems found
23 passed 5 warnings 1 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 mx include:spf.protection.outlook.com ip4:51.68.16.121 ip4:87.252.5.0/25 ip4:83.68.101.9 ip4:213.32.80.218 ip4:194.59.180.45 ip4:194.59.180.36/29 ip4:213.182.46.226 include:mailing.spf.ecritel.net ip4:213.182.46.226/29 ip4:87.98.187.73 ip4:51.68.95.78 ip4:51.83.35.24 ip4:51.91.150.238 ip4:162.19.0.112 include:spf.secutix.com a:newsletter.netlor.fr include:spf.sendinblue.com include:turbo-smtp.com include:spf.augure.com -all
DNS lookups
11 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    11 DNS lookups, over the limit of 10
    SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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

warn

p=quarantine (_dmarc.reims.fr)

Found

Record
v=DMARC1; p=quarantine; pct=100;rua=mailto:postmasterreims@reims.fr; ruf=mailto:postmasterreims@reims.fr; fo=1
Found at
_dmarc.reims.fr
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:postmasterreims@reims.frAggregate report addresses
rufmailto:postmasterreims@reims.frFailure report addresses
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:postmasterreims@reims.fr
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default, selector1, s1, s2

Found

Selectors
default, selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
selector1RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: default, selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: default, selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ 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

1 mail server

Found

PriorityHostRecordsReverse DNS
0reims-fr.mail.protection.outlook.comA 52.101.164.0 A 52.101.166.1 A 52.101.166.2 A 52.101.166.0 AAAA 2a01:111:f403:ca1e:: AAAA 2a01:111:f403:ca25::2 AAAA 2a01:111:f403:ca25::1 AAAA 2a01:111:f403:ca25::mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-paup264cu00202.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓ mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-paup264cu00202.inbound.protection.outlook.com ✓ mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
reims-fr.mail.protection.outlook.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