Mail domain report: swov.nl

SPF

pass

SPF record published

Found

Record: v=spf1 include:servers.mcsv.net include:spf.protection.outlook.com include:spf.sendinblue.com ip4:194.171.80.1/24 include:_spf.technoberg.com -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

warn

p=quarantine (_dmarc.swov.nl)

Found

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

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

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@swov.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: default, dkim, mail, email, k1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors: default, dkim, mail, email, k1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
default	revoked
dkim	revoked
mail	RSA 1024 bits
email	revoked
k1	revoked
selector2	RSA 1024 bits
google	revoked
zoho	revoked
mx	revoked
key	revoked
mta	revoked
pm	revoked
dkim-smtp	revoked
s1	revoked
s2	revoked

Checks

✓ Keys found: default, dkim, mail, email, k1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7

DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.

#23
✓ No problematic flags #24

No test mode or SHA-1-only keys. Revoked keys (empty p=), which is fine after a key rotation: default, dkim, email, k1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (1)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 24855
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
0	swov-nl.d-v1.mx.microsoft	A 52.101.103.39 A 52.101.73.145 A 52.101.103.140 A 52.101.91.21 AAAA 2a01:111:f403:ca48::e AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca48::c AAAA 2a01:111:f403:ca21::10	mail-miypr05cu00207.inbound.protection.outlook.com ✓ mail-am6pr02cu00301.inbound.protection.outlook.com ✓ mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-matpr05cu00105.inbound.protection.outlook.com ✓ mail-miypr03cu00206.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-miypr03cu00104.inbound.protection.outlook.com ✓ mail-matpr05cu00100.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
swov-nl.d-v1.mx.microsoft	3 1 1 54883cc5f1849331… 3 1 1 cfd68bde4129c00a… 2 0 1 c1ad7778796d20bc… 3 1 1 803f7447cc75b208… 2 0 1 ea7a25255d111fc3…	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