pix.fr

Checked 22 October 2026, 04:48 UTC · via 8.8.8.8
✗Problems found
27 passed 3 warnings 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.google.com include:spf.sendinblue.com include:sendgrid.net include:fdspfeuc.freshemail.io include:message-business.com ~all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

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

warn

p=quarantine (_dmarc.pix.fr)

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:rua@dmarc.brevo.com;
Found at
_dmarc.pix.fr
External report address
mailto:rua@dmarc.brevo.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:rua@dmarc.brevo.comAggregate report addresses

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:rua@dmarc.brevo.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, s1, s2

Found

Selectors
mail, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: mail, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (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

pass

5 mail servers

Found

PriorityHostRecordsReverse DNS
1aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1alcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5alt1.aspmx.l.google.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1brd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5alt2.aspmx.l.google.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10alt3.aspmx.l.google.comA 192.179.20.26 AAAA 2404:6800:4000:1027::1bncboms-in-f26.1e100.net ✓ ncboms-in-f27.1e100.net ✓
10alt4.aspmx.l.google.comA 192.178.158.27 AAAA 2404:6800:4013:813::1blcdels-in-f27.1e100.net ✓ lcdels-in-f27.1e100.net ✓

Checks

  • ✓ 5 MX records #9
    Found 5 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.
  • ✓ Redundant MX hosts #12
    Found 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · TLS-RPT · DANE on 0 of 5 MX hosts

Found

MTA-STS record
v=STSv1;id=1760448656091;
Policy URL
https://mta-sts.pix.fr/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.pix.fr/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.pix.fr on 127.0.0.53:53: no such host
TLS-RPT record
v=TLSRPTv1;rua=mailto:smtp-tls-reports@pix.fr;

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
alt3.aspmx.l.google.comnone-
alt4.aspmx.l.google.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 1760448656091.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.pix.fr/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.pix.fr on 127.0.0.53:53: no such host.
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:smtp-tls-reports@pix.fr
  • 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