Mail domain report: timing.nl

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:83.137.145.0/24 ip4:89.188.15.0/24 ip6:2a01:1b0:7999:402::/64 ip4:217.114.96.238 ip4:85.209.108.192/27 ip4:87.249.107.205 ip4:89.207.28.4 ip4:87.249.107.196 ip4:167.89.0.0/17 ip4:204.220.160.0/21 ip4:95.168.220.192/26 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ip4:82.201.64.228 ip4:205.201.128.0/20 ip4:148.105.8.0/21 ip4:198.37.153.132 ip4:104.40.229.156 ip4:52.169.0.179 ip4:20.50.220.144/28 ip4:40.127.253.48/28 ip4:85.214.60.41 ip4:81.169.234.199/32 ip4:81.169.242.205/32 ip4:85.214.235.145/32 ip4:81.169.234.114/32 ip4:149.72.88.121/32 ip4:79.174.130.64/27 ip4:213.171.151.80/29 ip4:178.208.56.145/28 ip4:79.174.134.160/28 ip4:185.46.182.1 ip4:185.46.182.200/29 ip4:185.46.182.208/31 ip4:95.168.207.80/28 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 ip4:185.136.64.128/27 ip4:159.183.0.0/16 ip4:185.211.208.10/32 ip4:185.136.65.128/27 ip4:88.86.113.160/27 ip4:185.18.11.16/29 ip4:82.208.41.201 ip4:198.2.128.0/18 ip4:86.105.244.9 ip4:86.105.244.3 ip4:86.105.244.8 ip4:198.2.186.0/23 ip4:205.201.131.0/24 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:185.6.160.213/32 include:_spf.eu.sparkpostmail.com include:amazonses.com include:turbo-smtp.com include:spf.sendinblue.com include:spf.protection.outlook.com include:spf.afas.online ~all
DNS lookups: 10 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 10 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.timing.nl)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:dmarc@timing.nl,mailto:dmarc_agg@vali.email;
Found at: _dmarc.timing.nl
External report address: mailto:dmarc_agg@vali.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:dmarc@timing.nl,mailto:dmarc_agg@vali.email	Aggregate report addresses

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@timing.nl, mailto:dmarc_agg@vali.email
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, k1, selector1, selector2, s1, s2

Found

Selectors: mail, k1, selector1, selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
k1	RSA 1024 bits
selector1	RSA 1024 bits
selector2	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: mail, k1, selector1, selector2, s1, s2 #7

DKIM keys found for this domain with selectors: mail, k1, selector1, selector2, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (1024 bits), selector1 (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

warn

Not signed

Found

DNSKEY records: No (0)
DS at parent: No

Checks

!

Not enabled

DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	timing-nl.mail.protection.outlook.com	A 52.101.91.162 A 52.101.91.156 A 52.101.73.123 A 52.101.73.126 AAAA 2a01:111:f403:ca09::24 AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:ca04::a	mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-maspr04cu00104.inbound.protection.outlook.com ✓ mail-am6pr02cu00203.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-am6pr02cu00204.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-du0pr03cu00102.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 0 of 1 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
timing-nl.mail.protection.outlook.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