Mail domain report: middelburg.nl

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:spf.simgroephosting01.nl include:_spf.zorgmail.nl include:spf.gouwit.hosting ip4:195.143.61.129 ip4:193.108.234.0/23 ip4:31.171.205.177 ip4:34.252.27.239 ip4:34.251.157.56 ip4:35.157.154.159 ip4:35.157.187.101 ip4:194.53.72.10 ip4:185.241.186.52 ip4:45.80.232.20/30 ip4:185.136.64.10 ip4:185.136.65.10 ip4:185.136.65.11 ip4:185.136.64.11 ip4:89.250.189.21 ip4:37.17.212.82 ip4:84.38.237.173 ip6:2a0a:9fc0:d:0:84:38:237:173 ip6:2a00:1fb8:a13:1::25 ip6:2001:4cb8:59c:1::25 ip4:194.53.72.4 ip4:194.53.72.252 ip4:31.223.173.49 ip4:45.80.232.22 ip4:212.115.205.163 ip4:90.145.221.134 ip4:81.246.113.58 ip4:80.247.174.68 ip4:81.246.113.50 ip4:212.72.62.129/27 ip4:205.201.133.57 ip4:87.249.113.154 ip4:34.249.196.78 ip4:193.177.166.3 ip6:2001:67c:45c:f018::3 ip6:2001:67c:45c:f018::2 ip6:2a02:120:380:1::4a ip4:90.145.221.138 ip6:2a02:120:380:1::91 ip4:185.136.64.128/27 ip4:185.136.65.128/27 ip4:87.251.35.5 ip4:31.171.205.186 ip4:77.222.78.0/28 ip4:37.48.91.17 -all
DNS lookups: 5 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

warn

p=quarantine (_dmarc.middelburg.nl)

Found

Record: v=DMARC1; p=quarantine; fo=d; rf=afrf; rua=mailto:systeembeheer@middelburg.nl; ruf=mailto:systeembeheer@middelburg.nl; sp=reject
Found at: _dmarc.middelburg.nl

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	reject	Subdomain policy
rua	mailto:systeembeheer@middelburg.nl	Aggregate report addresses
ruf	mailto:systeembeheer@middelburg.nl	Failure report addresses
fo	d	Failure reporting options
rf	afrf	Failure report format

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:systeembeheer@middelburg.nl
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, k1, selector1

Found

Selectors: mail, k1, selector1
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 2048 bits	h=sha256
k1	RSA 1024 bits
selector1	RSA 2048 bits

Checks

✓ Keys found: mail, k1, selector1 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: k1 (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 (2)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 47730, 49412
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
0	middelburg-nl.s-v1.mx.microsoft	A 52.101.181.156 A 52.101.68.25 A 52.101.103.140 A 52.101.73.123 AAAA 2a01:111:f403:ca48::e AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca04::f AAAA 2a01:111:f403:c967::8	mail-wa4pr05cu00104.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-am6pr02cu00203.inbound.protection.outlook.com ✓ mail-miypr03cu00206.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-db7pr03cu00507.inbound.protection.outlook.com ✓ mail-cpjpr04cu00100.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 1 of 1 MX hosts

Found

DANE (TLSA records)

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

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
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✓ 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