inpi.fr

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:87.252.5.56 ip4:87.252.0.103 ip4:87.252.0.74 ip4:82.210.44.24 ip4:82.210.44.25 ip4:82.210.44.74 ip4:82.210.44.124 ip4:82.210.44.125 ip4:82.210.44.126 ip4:82.210.44.127 -all
DNS lookups
0 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; aspf=s; rua=mailto:dmarc-rua@inpi.fr; ruf=mailto:dmarc-ruf@inpi.fr; fo=s;
Found at
_dmarc.inpi.fr
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:dmarc-rua@inpi.frAggregate report addresses
rufmailto:dmarc-ruf@inpi.frFailure report addresses
aspfsSPF alignment (r = relaxed, s = strict)
fosFailure reporting options

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:dmarc-rua@inpi.fr
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

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

6 mail servers

Found

PriorityHostRecordsReverse DNS
10mail1.inpi.frA 82.210.44.24mail1.inpi.fr ✓
10mail2.inpi.frA 82.210.44.25mail2.inpi.fr ✓
100mail3.inpi.frA 82.210.44.124mail3.inpi.fr ✓
100mail4.inpi.frA 82.210.44.125mail4.inpi.fr ✓
100mail5.inpi.frA 82.210.44.126mail5.inpi.fr ✓
100mail6.inpi.frA 82.210.44.127mail6.inpi.fr ✓

Checks

  • ✓ 6 MX records #9
    Found 6 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: mail1.inpi.fr, mail2.inpi.fr, mail3.inpi.fr, mail4.inpi.fr, mail5.inpi.fr, mail6.inpi.fr
    #11
  • ✓ Redundant MX hosts #12
    Found 6 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail1.inpi.frnone-
mail2.inpi.frnone-
mail3.inpi.frnone-
mail4.inpi.frnone-
mail5.inpi.frnone-
mail6.inpi.frnone-

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