ysl.com

Checked 22 October 2026, 11:41 UTC · via 8.8.8.8
!Passed with warnings
26 passed 5 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:13.111.87.2 ip4:13.111.87.3 ip4:13.111.20.176 include:_spf.salesforce.com ip4:194.206.254.0/24 ip4:195.24.246.0/23 ip4:195.42.251.0/24 ip4:217.109.67.0/24 ip4:193.104.231.0/24 ip4:67.192.194.205/32 ip4:67.192.194.206/32 ip4:119.73.240.71 ip4:119.73.240.74 ip4:203.116.33.183 ip4:64.73.120.224/27 ip4:213.41.42.80/28 ip4:180.87.182.9 ip4:142.0.177.24 ip4:142.0.187.58 include:spf-00168301.pphosted.com include:spf.protection.outlook.com include:spf.messagelabs.com include:spf.mailjet.com include:spf.mandrillapp.com -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.ysl.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:uhhmaygb@ag.eu.dmarcadvisor.com; ruf=mailto:uhhmaygb@fr.eu.dmarcadvisor.com
Found at
_dmarc.ysl.com
External report address
mailto:uhhmaygb@ag.eu.dmarcadvisor.com (authorized)
External report address
mailto:uhhmaygb@fr.eu.dmarcadvisor.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:uhhmaygb@ag.eu.dmarcadvisor.comAggregate report addresses
rufmailto:uhhmaygb@fr.eu.dmarcadvisor.comFailure report addresses

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

DKIM

warn

Selectors: mail, selector1, s1, s2

Found

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

Checks

  • ✓ Keys found: mail, selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, selector1, 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

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mail1.kering.netA 185.132.182.47mx08-00168301.pphosted.com ✓
10mail2.kering.netA 91.207.212.22mx07-00168301.pphosted.com ✓
20mail.pprgroup.netA 62.209.51.22no PTR

Checks

  • ✓ 3 MX records #9
    Found 3 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.kering.net, mail2.kering.net, mail.pprgroup.net
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 62.209.51.22 (mail.pprgroup.net). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail1.kering.netnone-
mail2.kering.netnone-
mail.pprgroup.netnone-

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://bimi-project-embeded-logos.s3.eu-west-1.amazonaws.com/order_498817264_logo.svg

Found

Record
v=BIMI1; l=https://bimi-project-embeded-logos.s3.eu-west-1.amazonaws.com/order_498817264_logo.svg; a=https://bimi-project-embeded-logos.s3.eu-west-1.amazonaws.com/kering_s_a.pem
Found at
default._bimi.ysl.com
Logo
https://bimi-project-embeded-logos.s3.eu-west-1.amazonaws.com/order_498817264_logo.svg
Certificate
https://bimi-project-embeded-logos.s3.eu-west-1.amazonaws.com/kering_s_a.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://bimi-project-embeded-logos.s3.eu-west-1.amazonaws.com/order_498817264_logo.svg; certificate: https://bimi-project-embeded-logos.s3.eu-west-1.amazonaws.com/kering_s_a.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.