knauf.fr

p=quarantine (_dmarc.knauf.fr)

Found

Record

v=DMARC1; p=quarantine; sp=reject; rua=mailto:1d2df9385cf844c58a9c6b10c7e6019f@dmarc-reports.cloudflare.net,mailto:dmarc_reports@knauf.com; ruf=mailto:Forensic_dmarc_reports@knauf.com; aspf=s; adkim=s;

Found at

_dmarc.knauf.fr

External report address

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

External report address

mailto:dmarc_reports@knauf.com (not authorized)

External report address

mailto:Forensic_dmarc_reports@knauf.com (not 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:1d2df9385cf844c58a9c6b10c7e6019f@dmarc-reports.cloudflare.net, mailto:dmarc_reports@knauf.com
• ✓ Subdomain policy: reject #20

  Subdomains are covered by policy 'reject'.
• !

  Report address not authorized

  These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc_reports@knauf.com (needs knauf.fr._report._dmarc.knauf.com); mailto:Forensic_dmarc_reports@knauf.com (needs knauf.fr._report._dmarc.knauf.com). Ask the report provider to publish the record, or check the address.

  #29

Selectors: k1, selector1, selector2

Found

Selectors

k1, selector1, selector2

_domainkey

NOERROR

Checks

• ✓ Keys found: k1, selector1, selector2 #7

  DKIM keys found for this domain with selectors: k1, selector1, selector2
• !

  1024-bit DKIM key

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

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: mailstream-eu1.mxrecord.io

  #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: 172.65.245.214 (mailstream-eu1.mxrecord.io). 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