grandparissud.fr

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:37.58.138.135 ip4:37.58.138.140 ip4:51.75.13.15 ip4:192.168.253.199 ip4:192.168.253.201 ip4:149.72.123.24 ip4:188.165.186.86 ip4:147.135.255.176 ip4:46.105.189.123 ip4:213.32.80.160 ip4:77.159.239.180 ip4:80.248.220.208 ip4:77.156.226.36 ip4:93.17.45.34 ip4:93.17.45.38 ip4:77.159.239.181 ip4:87.98.156.242 ip4:162.19.20.69 ip4:141.105.72.126 ip4:81.31.205.4 ip4:80.74.77.110 ip4:40.107.9.128 ip4:185.41.28.111 ip4:153.92.233.124 ip4:185.41.28.128 ip4:212.146.245.154 ip4:209.85.128.0/17 ip4:87.98.159.169 ip4:51.83.33.164 ip4:57.128.103.166 ip4:62.4.9.36 ip4:62.4.9.37 ip4:212.78.32.110 ip4:77.32.149.13 ip4:81.31.205.4 include:spf.protection.outlook.com include:spf.brevo.com include:sendgrid.net include:spf.matchmaking-studio.com include:spf.mailjet.com include:spf.somei.fr ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 8 of 10 DNS lookups #2
    SPF record needs 8 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

fail

p=none (_dmarc.grandparissud.fr)

Found

Record
v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com
Found at
_dmarc.grandparissud.fr
External report address
mailto:rua@dmarc.brevo.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:rua@dmarc.brevo.comAggregate report addresses

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:rua@dmarc.brevo.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector1

Found

Selectors
mail, selector1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1 #7
    DKIM keys found for this domain with selectors: mail, selector1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (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
0grandparissud-fr.mail.protection.outlook.comA 52.101.166.2 A 52.101.164.0 A 52.101.166.1 A 52.101.166.0 AAAA 2a01:111:f403:ca25::1 AAAA 2a01:111:f403:ca25:: AAAA 2a01:111:f403:ca1e:: AAAA 2a01:111:f403:ca25::2mail-paup264cu00202.inbound.protection.outlook.com ✓ mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓ mail-pr0p264cu01301.inbound.protection.outlook.com ✓ mail-pa5p264cu00200.inbound.protection.outlook.com ✓ mail-mrzp264cu00100.inbound.protection.outlook.com ✓ mail-paup264cu00202.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
grandparissud-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