boulangerie-ange.fr

SPF record published

Found

Record

v=spf1 ip4:213.152.3.83 ip4:5.226.2.176/28 ip4:87.98.189.168 ip4:87.98.189.168 ip4:91.121.52.196 ip4:91.121.57.59 ip4:195.154.113.94 ip4:178.32.99.37 ip4:147.135.227.252 ip4:137.74.84.0/24 ip4:217.182.118.0/27 ip4:185.209.208.0/22 ip4:51.77.79.146 ip4:198.2.133.152 ip4:168.245.122.239 include:spf.protection.outlook.com include:spf.brevo.com include:spf.protection.outlook.com include:spf.boulangerie-ange.fr include:spf.mailinblack.com mx -all

DNS lookups

6 of 10

Void lookups

1 of 2

Problem

include:spf.boulangerie-ange.fr does not exist or has no records

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• !

  6 of 10 DNS lookups, with problems

  SPF record needs 6 DNS lookups (limit is 10). Problems found: include:spf.boulangerie-ange.fr does not exist or has no records.

  #2
• ✓ 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.
• !

  1 void lookup

  1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.

  #26
• ✓ No overly broad IP ranges #27

  All ip4/ip6 ranges are narrow enough.

p=quarantine (_dmarc.boulangerie-ange.fr)

Found

Record

v=DMARC1; p=quarantine;

Found at

_dmarc.boulangerie-ange.fr

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

  No aggregate reports (rua)

  DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

  #19
• ✓ Subdomain policy: quarantine #20

  Subdomains are covered by policy 'quarantine'.

Selectors: mail, selector1, s1, s2

Found

Selectors

mail, selector1, s1, s2

_domainkey

NOERROR

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.

Signed, but no DS at parent

Found

DNSKEY records

Yes (2)

DS at parent

No

Algorithms

ECDSAP256SHA256 (13)

Key tags

34505, 2371

Signatures valid until

14 December 2026, 17:50 UTC

Checks

• !

  Signed, but no DS at parent

  The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

  #8
• ✓ Signatures valid until 2026-12-14 #21

  DNSKEY signatures are valid until 2026-12-14T17:50:12Z.

1 mail server

Found

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: mx-mibc-fr-10.mailinblack.com

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

  Addresses without reverse DNS

  These MX addresses have no PTR record, which many receivers treat as a spam signal: 20.216.139.123 (mx-mibc-fr-10.mailinblack.com). Ask your hosting provider to set one.

  #30

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

Found

DANE (TLSA records)

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