bonprix.fr

Checked 22 October 2026, 02:00 UTC · via 8.8.8.8
!Passed with warnings
24 passed 5 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:195.140.184.0/22 ip4:91.192.40.0/22 ip4:80.154.17.199/32 ip4:85.199.65.199/32 ip4:195.50.177.199/32 ip4:208.82.73.199/32 -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

pass

p=reject (_dmarc.bonprix.fr)

Found

Record
v=DMARC1; p=reject; rua=mailto:dmarc@bonprix.fr,mailto:qdnjvmy6@ag.eu.dmarcadvisor.com;
Found at
_dmarc.bonprix.fr
External report address
mailto:qdnjvmy6@ag.eu.dmarcadvisor.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:dmarc@bonprix.fr,mailto:qdnjvmy6@ag.eu.dmarcadvisor.comAggregate 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:dmarc@bonprix.fr, mailto:qdnjvmy6@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

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

1 mail server

Found

PriorityHostRecordsReverse DNS
10mail.delink-ssl.netA 46.4.207.193mail.delink-ssl.net ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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: mail.delink-ssl.net
    #11
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 1 MX address have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail.delink-ssl.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://vmc.digicert.com/53704f92-c104-4e96-8260-39df6ff4c355.svg

Found

Record
v=BIMI1;l=https://vmc.digicert.com/53704f92-c104-4e96-8260-39df6ff4c355.svg;a=https://vmc.digicert.com/53704f92-c104-4e96-8260-39df6ff4c355.pem
Found at
default._bimi.bonprix.fr
Logo
https://vmc.digicert.com/53704f92-c104-4e96-8260-39df6ff4c355.svg
Certificate
https://vmc.digicert.com/53704f92-c104-4e96-8260-39df6ff4c355.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/53704f92-c104-4e96-8260-39df6ff4c355.svg; certificate: https://vmc.digicert.com/53704f92-c104-4e96-8260-39df6ff4c355.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.