dammann.fr

SPF record published

Found

Record

v=spf1 a mx ip4:54.36.177.118 ip4:91.134.0.0/16 ip4:52.96.0.0/12 include:_spf.monarobase.net include:sendgrid.net include:spf.brevo.com include:spf.protection.outlook.com -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.
• !

  Broad IP ranges

  These ranges authorize tens of thousands of addresses or more: ip4:52.96.0.0/12. Check that you really own and send from all of them.

  #27

p=quarantine (_dmarc.dammann.fr)

Found

Record

v=DMARC1; p=quarantine; pct=10; rua=mailto:informatique@dammann.fr; ruf=mailto:informatique@dammann.fr; ri=86400

Found at

_dmarc.dammann.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 10% of mail

  DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.

  #18
• ✓ Aggregate reports enabled #19

  Aggregate reports are sent to: mailto:informatique@dammann.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.

Selectors: default, mail

Found

Selectors

default, mail

_domainkey

NOERROR

Checks

• ✓ Keys found: default, mail #7

  DKIM keys found for this domain with selectors: default, mail
• !

  1024-bit DKIM key

  1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), mail (1024 bits). Rotate to a 2048-bit key.

  #23
• ✓ No problematic flags #24

  No keys in test mode, revoked, or limited to SHA-1.

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

2 mail servers

Found

Checks

• ✓ 2 MX records #9

  Found 2 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-11.mailinblack.com, mx-mibc-fr-11.mailinblack.com

  #11
• ✓ Redundant MX hosts #12

  Found 2 MX records, which provides redundancy for email delivery.
• ✓ At most 5 MX records #13

  Found 2 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: 4.176.17.204 (mx-mibc-fr-11.mailinblack.com), 4.176.17.204 (mx-mibc-fr-11.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