Mail domain report: vorm.nl

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:195.189.23.246 ip4:77.74.54.75 ip4:77.74.54.216 ip4:80.95.170.195 ip4:46.31.48.0/21 ip6:2001:4c10:504:0:80:95:160:62 include:_spf.intermax.nl include:spf.hdconnect.nl include:spf.provalue.nl include:spf.protection.outlook.com include:spf_core.nbo.nl include:mailswitch.nl include:spf.mandrillapp.com include:spf.mailjet.com -all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

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

DMARC

warn

p=quarantine (_dmarc.vorm.nl)

Found

Record: v=DMARC1; p=quarantine; sp=quarantine; adkim=r; fo=1; ri=604800; rua=mailto:dmarc@vorm.nl; ruf=mailto:dmarc@vorm.nl
Found at: _dmarc.vorm.nl

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	quarantine	Subdomain policy
rua	mailto:dmarc@vorm.nl	Aggregate report addresses
ruf	mailto:dmarc@vorm.nl	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
fo	1	Failure reporting options
ri	604800	Report interval (seconds)

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:dmarc@vorm.nl
✓ Subdomain policy: quarantine #20

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

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector2, s1, s2

Found

Selectors: selector2, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: selector2, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: selector2 (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 (3)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 22938, 3547, 58500
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	vorm-nl.a-v1.mx.microsoft	A 52.101.73.145 A 52.101.91.156 A 52.101.68.21 A 52.101.68.15 AAAA 2a01:111:f403:c967::c AAAA 2a01:111:f403:ca21::10 AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca09::26	mail-am6pr02cu00301.inbound.protection.outlook.com ✓ mail-maspr04cu00104.inbound.protection.outlook.com ✓ mail-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-db6pr03cu00107.inbound.protection.outlook.com ✓ mail-cpjpr05cu00204.inbound.protection.outlook.com ✓ mail-matpr05cu00100.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.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
vorm-nl.a-v1.mx.microsoft	3 1 1 54883cc5f1849331… 2 0 1 ea7a25255d111fc3… 3 1 1 cfd68bde4129c00a… 3 1 1 803f7447cc75b208… 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