xcancel.com

p=reject (_dmarc.xcancel.com)

Found

Record

v=DMARC1; p=reject; rua=mailto:postmaster@unixfox.eu,mailto:8a8641fa-3002-4781-bd15-dc3f30b9cbf0@dmarc.scw-tem.cloud, mailto:dmarc_agg@vali.email; ruf=mailto:postmaster@unixfox.eu,mailto:8a8641fa-3002-4781-bd15-dc3f30b9cbf0@dmarc.scw-tem.cloud; fo=1

Found at

_dmarc.xcancel.com

External report address

mailto:postmaster@unixfox.eu (not authorized)

External report address

mailto:8a8641fa-3002-4781-bd15-dc3f30b9cbf0@dmarc.scw-tem.cloud (authorized)

External report address

mailto:dmarc_agg@vali.email (authorized)

Checks

• ✓ Policy: reject #4

  DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
• ✓ 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:postmaster@unixfox.eu, mailto:8a8641fa-3002-4781-bd15-dc3f30b9cbf0@dmarc.scw-tem.cloud, mailto:dmarc_agg@vali.email
• ✓ 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:postmaster@unixfox.eu (needs xcancel.com._report._dmarc.unixfox.eu). Ask the report provider to publish the record, or check the address.

  #29

Selectors: dkim, s1, s2

Found

Selectors

dkim, s1, s2

_domainkey

NOERROR

Checks

• ✓ Keys found: dkim, s1, s2 #7

  DKIM keys found for this domain with selectors: dkim, 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

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.
• !

  Hosts are CNAMEs

  MX records must point to a host name with A/AAAA records, not to a CNAME: mx.xcancel.com -> mx.emiliendevos.be

  #22
• !

  Addresses without reverse DNS

  These MX addresses have no PTR record, which many receivers treat as a spam signal: 152.70.188.178 (mx.xcancel.com), 152.67.94.22 (mx.xcancel.com). Ask your hosting provider to set one.

  #30

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

Found

MTA-STS record

v=STSv1; id=705348472672487978

Policy URL

https://mta-sts.xcancel.com/.well-known/mta-sts.txt

Mode

testing

Allowed MX

mx.emiliendevos.be

Max age

604800 seconds

TLS-RPT record

v=TLSRPTv1; rua=mailto:postmaster@emiliendevos.be

DANE (TLSA records)

Checks

• ✓ Record published #32

  MTA-STS record found with id 705348472672487978.
• !

  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: mx.emiliendevos.be): mx.xcancel.com. This will break delivery once the policy is enforced.

  #34
• ✓ Reports enabled #35

  TLS reports are sent to: mailto:postmaster@emiliendevos.be
• 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