Mail domain report: almere.nl

SPF

pass

SPF record published

Record: v=spf1 include:spf.almere.nl.eu-0nvswnoi.e1.dspf.app include:spfklant.pinkroccade.nl -all
DNS lookups: 8 of 10
Void lookups: 0 of 2

✓ No deprecated ptr mechanism #1

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

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

pass

p=reject (_dmarc.almere.nl)

Record: v=DMARC1; p=reject; rua=mailto:0nvswnoi@ag.eu.dmarcadvisor.com,mailto:rapportages@dmarc.ibdgemeenten.nl; ruf=mailto:0nvswnoi@fr.eu.dmarcadvisor.com;
Found at: _dmarc.almere.nl
External report address: mailto:0nvswnoi@ag.eu.dmarcadvisor.com (authorized)
External report address: mailto:rapportages@dmarc.ibdgemeenten.nl (authorized)
External report address: mailto:0nvswnoi@fr.eu.dmarcadvisor.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:0nvswnoi@ag.eu.dmarcadvisor.com,mailto:rapportages@dmarc.ibdgemeenten.nl	Aggregate report addresses
ruf	mailto:0nvswnoi@fr.eu.dmarcadvisor.com	Failure report addresses

✓ 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:0nvswnoi@ag.eu.dmarcadvisor.com, mailto:rapportages@dmarc.ibdgemeenten.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.

warn

Selectors: k1, selector1, selector2

✓ Keys found: k1, selector1, selector2 #7

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

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.

info

DNS query for almere.nl failed: read udp 46.225.38.91:38294->8.8.8.8:53: i/o timeout

warn

1 mail server

Priority	Host	Records	Reverse DNS
10	almere-nl.p-v1.mx.microsoft	A 52.101.68.10 A 52.101.91.162 A 52.101.185.21 A 52.101.68.29 AAAA 2a01:111:f403:ca21::10 AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca09::a	mail-dbbpr03cu00102.inbound.protection.outlook.com ✓ mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-zrxpr05cu00105.inbound.protection.outlook.com ✓ mail-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-matpr05cu00100.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓

✓ 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.

warn

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

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

!

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.

info

No BIMI record