sofcot.fr

Checked 22 October 2026, 05:16 UTC · via 8.8.8.8
✗Problems found
15 passed 8 warnings 1 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 mx mx:ex.mail.ovh.net include:spf.protection.outlook.com include:outlook.office365.com include:spf.mandrillapp.com ~all
DNS lookups
5 of 10
Void lookups
1 of 2
Problem
include:outlook.office365.com does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • !
    5 of 10 DNS lookups, with problems
    SPF record needs 5 DNS lookups (limit is 10). Problems found: include:outlook.office365.com does not exist or has no records.
    #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.
  • !
    1 void lookup
    1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.sofcot.fr)

Found

Record
v=DMARC1; p=none;
Found at
_dmarc.sofcot.fr
TagValueMeaning
vDMARC1Version
pnonePolicy

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
0sofcot-fr.mail.protection.outlook.comA 52.101.166.2 A 52.101.166.1 A 52.101.164.0 A 52.101.166.0 AAAA 2a01:111:f403:ca25::1 AAAA 2a01:111:f403:ca25::2 AAAA 2a01:111:f403:ca1e:: AAAA 2a01:111:f403:ca25::mail-paup264cu00202.inbound.protection.outlook.com ✓ mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓ mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-paup264cu00202.inbound.protection.outlook.com ✓ mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓
32767ms35182786.msv1.invalid(does not resolve)

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: ms35182786.msv1.invalid
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: ms35182786.msv1.invalid
    #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 8 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
sofcot-fr.mail.protection.outlook.comnone-
ms35182786.msv1.invalidnone-

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