onlc.fr

SPF record published

Found

Record

v=spf1 mx a ip4:217.182.192.144 ip4:91.121.61.163 include:spf.onlinecreation.fr ip4:185.26.104.0/22 ?all

DNS lookups

3 of 10

Void lookups

0 of 2

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• ✓ 3 of 10 DNS lookups #2

  SPF record needs 3 DNS lookups (limit is 10).
• !

  Ends with ?all (neutral)

  SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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

p=quarantine (_dmarc.onlc.fr)

Found

Record

v=DMARC1; p=quarantine; rua=mailto:b8f885426b264f7d965b86a95e333aa7@dmarc-reports.cloudflare.net

Found at

_dmarc.onlc.fr

External report address

mailto:b8f885426b264f7d965b86a95e333aa7@dmarc-reports.cloudflare.net (authorized)

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.
• ✓ Aggregate reports enabled #19

  Aggregate reports are sent to: mailto:b8f885426b264f7d965b86a95e333aa7@dmarc-reports.cloudflare.net
• ✓ Subdomain policy: quarantine #20

  Subdomains are covered by policy 'quarantine'.
• ✓ External report addresses authorized #29

  Report addresses in other domains have published their authorization.

Selectors: s1, s2

Found

Selectors

s1, s2

_domainkey

NOERROR

Checks

• ✓ Keys found: s1, s2 #7

  DKIM keys found for this domain with selectors: s1, s2
• !

  1024-bit DKIM key

  1024-bit RSA keys are the minimum and are considered weak today: 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.

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: mx1.netim.net, mx2.netim.net

  #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.
• ✓ Reverse DNS confirmed #30

  All 2 MX addresss have a PTR record that resolves back to them.

no MTA-STS · no TLS-RPT · DANE on 0 of 2 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