Mail domain report: rtc.be

SPF

pass

SPF record published

Found

Record: v=spf1 a mx ip4:91.183.186.72 ip4:51.15.253.103 ip4:141.95.203.11 ip4:91.183.33.224 ip4:91.183.33.147 ip4:85.26.37.145 ip4:5.196.62.239 ip4:82.212.178.234 ip4:188.65.218.77 include:spf.protection.outlook.com ~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 #3

SPF record properly uses ~all to restrict unauthorized senders.
✓ 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.

DMARC

fail

p=none (_dmarc.rtc.be)

Found

Record: v=DMARC1; p=none; pct=100; rua=mailto:re+zfsbfh55lrc@dmarc.postmarkapp.com; sp=none; aspf=r;
Found at: _dmarc.rtc.be
External report address: mailto:re+zfsbfh55lrc@dmarc.postmarkapp.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:re+zfsbfh55lrc@dmarc.postmarkapp.com	Aggregate report addresses
aspf	r	SPF alignment (r = relaxed, s = strict)

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:re+zfsbfh55lrc@dmarc.postmarkapp.com
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NOERROR

Checks

!

No key under common selectors

The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

#7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (1)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 33226
Signatures valid until: 5 November 2026, 00:00 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
✓ Signatures valid until 2026-11-05 #21

DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	rtc-be.mail.protection.outlook.com	A 52.101.209.153 A 52.101.103.39 A 52.101.68.8 A 52.101.91.21 AAAA 2a01:111:f403:ca09::a AAAA 2a01:111:f403:ca48::8 AAAA 2a01:111:f403:ca48::e AAAA 2a01:111:f403:ca21::8	mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-miypr05cu00207.inbound.protection.outlook.com ✓ mail-du0pr03cu00100.inbound.protection.outlook.com ✓ mail-matpr05cu00105.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓ mail-miypr03cu00206.inbound.protection.outlook.com ✓ mail-matpr04cu00100.inbound.protection.outlook.com ✓

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
rtc-be.mail.protection.outlook.com	none	-

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

BIMI

info

No BIMI record

Checks

i

Not configured

BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.

#38