Mail domain report: fnv.nl

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:51.124.150.188/32 ip4:159.100.65.240/28 ip4:159.100.66.0/28 ip4:81.93.164.103/32 ip4:81.93.173.201/32 ip4:167.89.100.176/32 ip4:82.161.224.157/32 include:spf.protection.outlook.com include:mailswitch.nl include:spf.mailjet.com include:spf.messagelabs.com include:_spf.zivver.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

fail

p=none (_dmarc.fnv.nl)

Found

Record: v=DMARC1;p=none;pct=100;ruf=mailto:dmarc-forensic@fnv.nl;rua=mailto:dmarc-aggregate@fnv.nl
Found at: _dmarc.fnv.nl

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-aggregate@fnv.nl	Aggregate report addresses
ruf	mailto:dmarc-forensic@fnv.nl	Failure report addresses

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:dmarc-aggregate@fnv.nl
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, s1, s2

Found

Selectors: selector1, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: selector1, s1, s2 #7

DKIM keys found for this domain with selectors: selector1, 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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (1)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 50515
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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	cluster1.eu.messagelabs.com	A 195.245.231.74 A 195.245.230.192 A 195.245.231.67 A 85.158.142.213 A 195.245.230.197 A 85.158.142.217	mail878.messagelabs.com ✓ mail850.messagelabs.com ✓ mail872.messagelabs.com ✓ mail837.messagelabs.com ✓ mail855.messagelabs.com ✓ mail830.messagelabs.com ✓
20	cluster1a.eu.messagelabs.com	A 34.91.159.228	228.159.91.34.bc.googleusercontent.com ✓

Checks

✓ 2 MX records #9

Found 2 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: cluster1.eu.messagelabs.com, cluster1a.eu.messagelabs.com

#11
✓ Redundant MX hosts #12

Found 2 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 2 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 7 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
cluster1.eu.messagelabs.com	none	-
cluster1a.eu.messagelabs.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

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