Mail domain report: topparken.nl

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:mail.zendesk.com include:_spf.paytsoftware.com include:spf.eu.exclaimer.net -all
DNS lookups: 4 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 4 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.topparken.nl)

Found

Record: v=DMARC1;p=none
Found at: _dmarc.topparken.nl

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy

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

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19

DKIM

warn

Selectors: selector1, google, s1, s2

Found

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

Selector	Key	Flags
selector1	RSA 2048 bits
google	public key is not valid base64
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

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

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

Unreadable DKIM key

These keys could not be parsed, so signatures made with them will fail: google (public key is not valid base64).

#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: ECDSAP256SHA256 (13)
Key tags: 31682, 39095
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

6 mail servers

Found

Priority	Host	Records	Reverse DNS
1	SMTP.GOOGLE.com	A 142.251.127.26 A 142.251.127.27 A 64.233.167.27 AAAA 2a00:1450:4001:c21::1b AAAA 2a00:1450:400c:c0a::1a AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ wl-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ wl-in-x1a.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
2	ASPMX.L.GOOGLE.com	A 74.125.206.26 AAAA 2a00:1450:4001:c21::1b	wk-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 172.253.152.27 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10	ALT3.ASPMX.L.GOOGLE.com	A 192.179.20.27 AAAA 2a00:1450:4025:4403::1b	ncboms-in-f27.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

✓ 6 MX records #9

Found 6 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 6 MX records, which provides redundancy for email delivery.
!

More than 5 MX records

Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

#13
✓ 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 16 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
SMTP.GOOGLE.com	none	-
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