carigami.fr

p=quarantine (_dmarc.carigami.fr)

Found

Record

v=DMARC1; p=quarantine; rua=mailto:dmarc-aggregate@floyt.com; ruf=mailto:dmarc-failures@floyt.com; fo=1;

Found at

_dmarc.carigami.fr

External report address

mailto:dmarc-aggregate@floyt.com (not authorized)

External report address

mailto:dmarc-failures@floyt.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:dmarc-aggregate@floyt.com
• ✓ Subdomain policy: quarantine #20

  Subdomains are covered by policy 'quarantine'.
• !

  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-aggregate@floyt.com (needs carigami.fr._report._dmarc.floyt.com); mailto:dmarc-failures@floyt.com (needs carigami.fr._report._dmarc.floyt.com). Ask the report provider to publish the record, or check the address.

  #29

Selectors: k1, google

Found

Selectors

k1, google

_domainkey

NOERROR

Checks

• ✓ Keys found: k1, google #7

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

  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.
• ✓ All hosts have IPv6 #11

  All MX records resolve to IPv6 addresses.
• !

  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 4 MX addresss have a PTR record that resolves back to them.

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

Found

MTA-STS record

v=STSv1;id=1764160223743;

Policy URL

https://mta-sts.carigami.fr/.well-known/mta-sts.txt

Mode

enforce

Allowed MX

smtp.google.com

Max age

86400 seconds

DANE (TLSA records)

Checks

• ✓ Record published #32

  MTA-STS record found with id 1764160223743.
• ✓ Policy enforced #33

  The MTA-STS policy is enforced and cached for 24h0m0s.
• ✓ All MX hosts covered #34

  Every MX host matches an mx: line of the MTA-STS policy.
• !

  Not configured

  MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

  #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