Mail domain report: perssupport.nl

SPF

warn

SPF record published

Found

Record: v=spf1 mx ptr ip4:188.118.6.0/24 include:_spf.google.com include:o1.release.perssupport.nl include:sendgrid.net include:_spf.mlsend.com ~all
DNS lookups: 7 of 10
Void lookups: 1 of 2
Problem: include:o1.release.perssupport.nl does not exist or has no records

Checks

!

Uses deprecated ptr mechanism

The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.

#1
!

7 of 10 DNS lookups, with problems

SPF record needs 7 DNS lookups (limit is 10). Problems found: include:o1.release.perssupport.nl does not exist or has no records.

#2
✓ 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.
!

1 void lookup

1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.

#26
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.perssupport.nl)

Found

Record: v=DMARC1; p=none; rua=mailto:dmarc@anp.eu; ruf=mailto:dmarc@anp.eu; pct=100;
Found at: _dmarc.perssupport.nl
External report address: mailto:dmarc@anp.eu (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc@anp.eu	Aggregate report addresses
ruf	mailto:dmarc@anp.eu	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@anp.eu
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: s1, s2

Found

Selectors: s1, s2
_domainkey: NOERROR

Selector	Key	Flags
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: 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 (2)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 13141, 1018
Signatures valid until: 9 November 2026, 13:49 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-09 #21

DNSKEY signatures are valid until 2026-11-09T13:49:24Z.

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 74.125.71.26 AAAA 2a00:1450:4001:c21::1b	wn-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	alt1.aspmx.l.google.com	A 192.178.213.27 AAAA 2a00:1450:4025:c01::1b	yugrqzs-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5	alt2.aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4010:c22::1a	lcfrai-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10	alt3.aspmx.l.google.com	A 192.179.20.26 AAAA 2a00:1450:4025:4403::1b	ncboms-in-f26.1e100.net ✓ yuskelf-in-f27.1e100.net ✓
10	alt4.aspmx.l.google.com	A 192.178.158.26 AAAA 2404:6800:4013:813::1a	lcdels-in-f26.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

✓ 5 MX records #9

Found 5 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.
✓ Redundant MX hosts #12

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

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.google.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