smile.fr

Checked 22 October 2026, 05:15 UTC · via 8.8.8.8
!Passed with warnings
23 passed 6 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:_spf.google.com include:_spf.alterway.fr include:_spf.smile.fr include:spf.mandrillapp.com include:6113121.spf02.hubspotemail.net ip4:213.162.49.10 ip4:91.216.209.254 ip4:91.216.209.194 ip4:213.91.10.23 ip4:46.105.116.120 -all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=reject; sp=none; pct=100; ri=86400; rua=mailto:it-departement@smile.fr
Found at
_dmarc.smile.fr
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:it-departement@smile.frAggregate report addresses
ri86400Report interval (seconds)

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:it-departement@smile.fr
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, k1, google

Found

Selectors
mail, k1, google
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
k1RSA 1024 bits
googleRSA 1024 bits

Checks

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

7 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.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::1byulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10ALT3.ASPMX.L.GOOGLE.COMA 192.179.20.27 AAAA 2404:6800:4000:1027::1bncboms-in-f27.1e100.net ✓ ncboms-in-f27.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 ✓
50bastion01.ovh.smile.frA 176.31.238.62bastion01.ovh.smile.fr ✓
50bastion02.ovh.smile.frA 51.91.219.73bastion02.ovh.smile.fr ✓

Checks

  • ✓ 7 MX records #9
    Found 7 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: bastion01.ovh.smile.fr, bastion02.ovh.smile.fr
    #11
  • ✓ Redundant MX hosts #12
    Found 7 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 7 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 12 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 7 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-
bastion01.ovh.smile.frnone-
bastion02.ovh.smile.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