privacycommission.be

p=quarantine (_dmarc.privacycommission.be)

Found

Record

v=DMARC1; p=quarantine; rua=mailto:msfj3rrr9w@rua.paladin.cheops.support; ruf=mailto:msfj3rrr9w@ruf.paladin.cheops.support; fo=1; t=n;

Found at

_dmarc.privacycommission.be

External report address

mailto:msfj3rrr9w@rua.paladin.cheops.support (authorized)

External report address

mailto:msfj3rrr9w@ruf.paladin.cheops.support (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:msfj3rrr9w@rua.paladin.cheops.support
• ✓ 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: selector1, selector2

Found

Selectors

selector1, selector2

_domainkey

NOERROR

Checks

• ✓ Keys found: selector1, selector2 #7

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

  1024-bit DKIM key

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

  #23
• ✓ No problematic flags #24

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

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: apd-gba-be-1.fortimailcloud.com, apd-gba-be-2.fortimailcloud.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.
• ✓ Reverse DNS confirmed #30

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

MTA-STS testing · TLS-RPT · DANE on 0 of 2 MX hosts

Found

MTA-STS record

v=STSv1; id=20250513154552953028;

Policy URL

https://mta-sts.privacycommission.be/.well-known/mta-sts.txt

Mode

testing

Allowed MX

gw000111-eu.fortimail.com

Max age

86400 seconds

TLS-RPT record

v=TLSRPTv1;rua=mailto:msfj3rrr9w@tls.paladin.cheops.support

DANE (TLSA records)

Checks

• ✓ Record published #32

  MTA-STS record found with id 20250513154552953028.
• !

  Policy in testing mode

  With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

  #33
• !

  MX hosts missing from policy

  These MX hosts are not listed in the MTA-STS policy (mx: gw000111-eu.fortimail.com): apd-gba-be-1.fortimailcloud.com, apd-gba-be-2.fortimailcloud.com. This will break delivery once the policy is enforced.

  #34
• ✓ Reports enabled #35

  TLS reports are sent to: mailto:msfj3rrr9w@tls.paladin.cheops.support
• 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