indy.fr

Checked 22 October 2026, 03:27 UTC · via 8.8.8.8
!Passed with warnings
28 passed 3 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.google.com include:_spf.mailgun.org include:_spf.eu.mailgun.org include:sendgrid.net include:servers.mcsv.net include:spf.mailjet.com include:mail.zendesk.com ~all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@indy.fr
Found at
_dmarc.indy.fr
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@indy.frAggregate 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:dmarc@indy.fr
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

pass

Selectors: google

Found

Selectors
google
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits

Checks

  • ✓ Keys found: google #7
    DKIM keys found for this domain with selectors: google
  • ✓ Strong keys #23
    DKIM keys are strong enough: google: RSA 2048 bits.
  • ✓ 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.27 AAAA 2a00:1450:4001:c21::1blcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5alt1.aspmx.l.google.comA 142.250.147.26 AAAA 2a00:1450:4025:c01::1ard-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
5alt2.aspmx.l.google.comA 172.253.152.27 AAAA 2a00:1450:4010:c22::1byulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10alt3.aspmx.l.google.comA 192.179.20.27 AAAA 2404:6800:4000:1027::1ancboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
10alt4.aspmx.l.google.comA 192.178.158.27 AAAA 2404:6800:4013:813::1alcdels-in-f27.1e100.net ✓ lcdels-in-f26.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

warn

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

Found

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

  • !
    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

pass

https://vmc.digicert.com/a32da7d8-a67f-4cb8-b6bd-d8652edaf2e7.svg

Found

Record
v=BIMI1; l=https://vmc.digicert.com/a32da7d8-a67f-4cb8-b6bd-d8652edaf2e7.svg; a=https://vmc.digicert.com/a32da7d8-a67f-4cb8-b6bd-d8652edaf2e7.pem; avp=personal
Found at
default._bimi.indy.fr
Logo
https://vmc.digicert.com/a32da7d8-a67f-4cb8-b6bd-d8652edaf2e7.svg
Certificate
https://vmc.digicert.com/a32da7d8-a67f-4cb8-b6bd-d8652edaf2e7.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/a32da7d8-a67f-4cb8-b6bd-d8652edaf2e7.svg; certificate: https://vmc.digicert.com/a32da7d8-a67f-4cb8-b6bd-d8652edaf2e7.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.