Mail domain report: vwe.nl

SPF

pass

SPF record published

Found

Record: v=spf1 include:amazonses.com include:spf.protection.outlook.com include:servers.mcsv.net include:spf.mandrillapp.com include:businessmonitor.nl include:spf-de.emailsignatures365.com include:_spf.psm.knowbe4.com include:spf.directdevice.info +ip4:80.85.160.88 +ip4:80.85.160.114 +ip4:80.85.160.19 +ip4:80.85.160.18 +ip4:80.85.160.12 +ip4:80.85.160.2 +ip4:185.175.25.103 +ip4:185.175.25.102 +ip4:82.94.207.128/25 +ip4:144.76.82.228 +ip4:81.171.29.77 +ip4:52.29.184.146 -all
DNS lookups: 9 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 9 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.vwe.nl)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:16a2314218964250a20e01262351d7d0@dmarc-reports.cloudflare.net,mailto:65cdd9376e67c@ag.dmarcly.com; ruf=mailto:65cdd9376e67c@fo.dmarcly.com; sp=quarantine; fo=0;
Found at: _dmarc.vwe.nl
External report address: mailto:16a2314218964250a20e01262351d7d0@dmarc-reports.cloudflare.net (authorized)
External report address: mailto:65cdd9376e67c@ag.dmarcly.com (authorized)
External report address: mailto:65cdd9376e67c@fo.dmarcly.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	quarantine	Subdomain policy
rua	mailto:16a2314218964250a20e01262351d7d0@dmarc-reports.cloudflare.net,mailto:65cdd9376e67c@ag.dmarcly.com	Aggregate report addresses
ruf	mailto:65cdd9376e67c@fo.dmarcly.com	Failure report addresses
fo	0	Failure reporting options

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:16a2314218964250a20e01262351d7d0@dmarc-reports.cloudflare.net, mailto:65cdd9376e67c@ag.dmarcly.com
✓ Subdomain policy: quarantine #20

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

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors: selector1, selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 1024 bits
selector2	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: selector1, selector2, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), s2 (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

warn

Not signed

Found

DNSKEY records: No (0)
DS at parent: No

Checks

!

Not enabled

DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	vwe-nl.mail.protection.outlook.com	A 52.101.103.140 A 52.101.73.155 A 52.101.103.137 A 52.101.91.153 AAAA 2a01:111:f403:ca21::e AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca09::22 AAAA 2a01:111:f403:c967::8	mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-am7pr02cu00203.inbound.protection.outlook.com ✓ mail-miypr02cu00101.inbound.protection.outlook.com ✓ mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-matpr04cu00306.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-am7pr02cu00302.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 0 of 1 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
vwe-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

warn

https://vwe.nl/wp-content/uploads/2026/06/Beeldmerk-VWE_RGB.svg

Found

Record: v=BIMI1; l=https://vwe.nl/wp-content/uploads/2026/06/Beeldmerk-VWE_RGB.svg; a=;
Found at: default._bimi.vwe.nl
Logo: https://vwe.nl/wp-content/uploads/2026/06/Beeldmerk-VWE_RGB.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.