europcar.fr

Checked 22 October 2026, 02:49 UTC · via 8.8.8.8
✗Problems found
13 passed 6 warnings 1 failed 4 info

SPF

pass

SPF record published

Found

Record
v=spf1 -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

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

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
100europcar.fr.s200a1.psmtp.com(does not resolve)
200europcar.fr.s200a2.psmtp.com(does not resolve)
300europcar.fr.s200b1.psmtp.com(does not resolve)
400europcar.fr.s200b2.psmtp.com(does not resolve)
500mx1.europcar.frA 193.222.134.2lookup failed
600mx2.europcar.frA 193.222.134.3lookup failed

Checks

  • ✓ 6 MX records #9
    Found 6 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: europcar.fr.s200a1.psmtp.com, europcar.fr.s200a2.psmtp.com, europcar.fr.s200b1.psmtp.com, europcar.fr.s200b2.psmtp.com
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: europcar.fr.s200a1.psmtp.com, europcar.fr.s200a2.psmtp.com, europcar.fr.s200b1.psmtp.com, europcar.fr.s200b2.psmtp.com, mx1.europcar.fr, mx2.europcar.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.
  • i
    Could not be checked
    The reverse lookup failed for: 193.222.134.2, 193.222.134.3.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
europcar.fr.s200a1.psmtp.comnone-
europcar.fr.s200a2.psmtp.comnone-
europcar.fr.s200b1.psmtp.comnone-
europcar.fr.s200b2.psmtp.comnone-
mx1.europcar.frnone-
mx2.europcar.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