Mail domain report: nza.nl

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:_spf.mailplus.nl include:spf.topdesk.net include:_spf.ubeeo.nl include:spf.afas.online include:_spf.zivver.com include:spf.formdesk.com ~all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 7 of 10 DNS lookups #2

SPF record needs 7 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

pass

p=reject (_dmarc.nza.nl)

Found

Record: v=DMARC1; p=reject; rua=mailto:dmarc@zorgautoriteit.uriports.com,mailto:dmarc@nza.nl
Found at: _dmarc.nza.nl
External report address: mailto:dmarc@zorgautoriteit.uriports.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:dmarc@zorgautoriteit.uriports.com,mailto:dmarc@nza.nl	Aggregate report addresses

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:dmarc@zorgautoriteit.uriports.com, mailto:dmarc@nza.nl
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: selector1, selector2

Found

Selectors: selector1, selector2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits
selector2	RSA 2048 bits

Checks

✓ Keys found: selector1, selector2 #7

DKIM keys found for this domain with selectors: selector1, selector2
✓ Strong keys #23

DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
✓ 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: 9947
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	nza-nl.p-v1.mx.microsoft	A 52.101.185.21 A 52.101.103.36 A 52.101.103.140 A 52.101.68.8 AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:ca09::20 AAAA 2a01:111:f403:c967::8 AAAA 2a01:111:f403:ca04::4	mail-zrxpr05cu00105.inbound.protection.outlook.com ✓ mail-miypr05cu00104.inbound.protection.outlook.com ✓ mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-du0pr03cu00100.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-as8pr05cu00400.inbound.protection.outlook.com ✓ mail-cpjpr04cu00100.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.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

fail

MTA-STS record without policy · TLS-RPT · DANE on 1 of 1 MX hosts

Found

MTA-STS record: v=STSv1; id=20250325152830Z;
Policy URL: https://mta-sts.nza.nl/.well-known/mta-sts.txt
Policy error: Get "https://mta-sts.nza.nl/.well-known/mta-sts.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
TLS-RPT record: v=TLSRPTv1; rua=mailto:tlsrpt@zorgautoriteit.uriports.com

DANE (TLSA records)

MX host	TLSA	DNSSEC
nza-nl.p-v1.mx.microsoft	3 1 1 cfd68bde4129c00a… 3 1 1 803f7447cc75b208… 2 0 1 ea7a25255d111fc3… 3 1 1 54883cc5f1849331… 2 0 1 c1ad7778796d20bc…	Yes

Checks

✓ Record published #32

MTA-STS record found with id 20250325152830Z.
✗

Policy not reachable

The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.nza.nl/.well-known/mta-sts.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers).

#33
✓ Reports enabled #35

TLS reports are sent to: mailto:tlsrpt@zorgautoriteit.uriports.com
✓ DANE on all MX hosts #36

All 1 MX host publish DNSSEC-validated TLSA records.

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