Mail domain report: rijnmond.nl

SPF

fail

SPF record published

Found

Record: v=spf1 mx ip4:144.178.246.68 ip4:144.178.246.80 ip4:92.111.214.221 ip4:90.145.68.205 include:_spf.salesforce.com include:spf.protection.outlook.com include:spf.topdesk.net include:_spf.google.com include:_spf.spotler.email include:spf.EU.exclaimer.net include:mailservers.elvy.nl include:5751016.spf02.hubspotemail.net include:_spf.holmsecurity.com -all
DNS lookups: 14 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

14 DNS lookups, over the limit of 10

SPF record needs 14 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#2
✓ 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.rijnmond.nl)

Found

Record: v=DMARC1; p=none; sp=none; pct=100; ri=86400; adkim=r; aspf=s; rua=mailto:dmarc-reports@rijnmond.nl; ruf=mailto:dmarc-reports@rijnmond.nl;
Found at: _dmarc.rijnmond.nl

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-reports@rijnmond.nl	Aggregate report addresses
ruf	mailto:dmarc-reports@rijnmond.nl	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF alignment (r = relaxed, s = strict)
ri	86400	Report interval (seconds)

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:dmarc-reports@rijnmond.nl
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector1, google

Found

Selectors: mail, selector1, google
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
selector1	RSA 2048 bits
google	RSA 2048 bits

Checks

✓ Keys found: mail, selector1, google #7

DKIM keys found for this domain with selectors: mail, selector1, google
!

1024-bit DKIM key

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

#23
✓ No problematic flags #24

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

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (1)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 10309
Signatures valid until: 29 October 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-10-29 #21

DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	rijnmond-nl.mail.protection.outlook.com	A 52.101.68.8 A 52.101.73.120 A 52.101.103.140 A 52.101.103.137 AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:ca04::9 AAAA 2a01:111:f403:ca09::a AAAA 2a01:111:f403:ca04::10	mail-du0pr03cu00100.inbound.protection.outlook.com ✓ mail-am7pr02cu00300.inbound.protection.outlook.com ✓ mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-miypr02cu00101.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-db7pr03cu00601.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.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
rijnmond-nl.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