Mail domain report: overstappen.nl

SPF

pass

SPF record published

Found

Record: v=spf1 a ip4:87.233.6.96/27 ip4:87.233.197.242 include:_spf.google.com ip4:50.31.36.179 include:sendgrid.net ip4:54.240.51.208 ip4:54.240.51.209 ip4:54.240.51.210 include:amazonses.com ip4:5.178.65.64/27 ip4:193.75.92.155 ip4:193.75.92.156 ip4:91.123.56.240 ip4:91.123.56.241 include:_spf.z-advies.nl -all
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 6 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.overstappen.nl)

Found

Record: v=DMARC1; p=none; pct=100; rua=mailto:dmarc@overstappen.nl; ruf=mailto:dmarc@overstappen.nl; sp=quarantine; fo=1;
Found at: _dmarc.overstappen.nl

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	quarantine	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc@overstappen.nl	Aggregate report addresses
ruf	mailto:dmarc@overstappen.nl	Failure report addresses
fo	1	Failure reporting options

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@overstappen.nl
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: google, s1, s2

Found

Selectors: google, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: google, s1, s2 #7

DKIM keys found for this domain with selectors: google, 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: ECDSAP256SHA256 (13)
Key tags: 6293, 62644
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

1 mail server

Found

Priority	Host	Records	Reverse DNS
1	SMTP.GOOGLE.com	A 142.251.127.26 A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓

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 4 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
SMTP.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