Mail domain report: leatherman.com

SPF

fail

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:spf.mandrillapp.com include:mailgun.org a:mail.leatherman.com a:production.web.leatherman.demandware.net ip4:45.62.180.133/32 ip4:209.170.239.237/32 ip4:52.183.35.31/32 ip4:208.86.168.7/32 ip4:135.84.68.123/32 -all
DNS lookups: 11 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

11 DNS lookups, over the limit of 10

SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#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.
✓ No void lookups #26

All include/redirect targets exist.
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.leatherman.com)

Found

Record: v=DMARC1; p=reject; pct=100; ruf=mailto:spam@leatherman.com;rua=mailto:spam@leatherman.com
Found at: _dmarc.leatherman.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:spam@leatherman.com	Aggregate report addresses
ruf	mailto:spam@leatherman.com	Failure report addresses

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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:spam@leatherman.com
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, s1, s2

Found

Selectors: selector1, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: selector1, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: 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
1	leatherman-com.mail.protection.outlook.com	A 52.101.60.68 A 52.101.41.122 A 52.101.194.152 A 52.101.60.71 AAAA 2a01:111:f403:f909::5 AAAA 2a01:111:f403:c95d::6 AAAA 2a01:111:f403:c946::1 AAAA 2a01:111:f403:c903::3	mail-bnypr02cu00104.inbound.protection.outlook.com ✓ mail-byapr02cu00302.inbound.protection.outlook.com ✓ mail-ch4pr04cu00300.inbound.protection.outlook.com ✓ mail-bn0pr02cu00307.inbound.protection.outlook.com ✓ mail-bn0pr04cu00805.inbound.protection.outlook.com ✓ mail-ph0pr02cu00106.inbound.protection.outlook.com ✓ mail-ch1pr04cu00101.inbound.protection.outlook.com ✓ mail-mw2pr02cu00503.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
leatherman-com.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

pass

https://vmcstoarge.z5.web.core.windows.net/LeathermanLogo.svg

Found

Record: v=BIMI1; l=https://vmcstoarge.z5.web.core.windows.net/LeathermanLogo.svg; a=https://vmcstoarge.z5.web.core.windows.net/leatherman_tool_group_inc.pem;
Found at: default._bimi.leatherman.com
Logo: https://vmcstoarge.z5.web.core.windows.net/LeathermanLogo.svg
Certificate: https://vmcstoarge.z5.web.core.windows.net/leatherman_tool_group_inc.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmcstoarge.z5.web.core.windows.net/LeathermanLogo.svg; certificate: https://vmcstoarge.z5.web.core.windows.net/leatherman_tool_group_inc.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.