Mail domain report: stryker.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:servers.mcsv.net include:mktomail.com include:spf.protection.outlook.com include:_spf.salesforce.com ip4:213.95.132.52 ip4:64.136.252.175 ip4:64.136.252.176 ip4:64.238.211.94 ip4:50.203.11.54 ip4:66.162.128.50 ip4:148.163.142.96 ip4:148.163.146.125 a:web.q4press.com include:spf.mandrillapp.com include:et._spf.pardot.com include:bpopen.capgemini.com ip4:192.200.190.165/30 ip4:104.195.80.16/28 ip4:192.200.181.144/28 ip4:174.37.85.64/28 ip4:75.126.150.248/30 ip4:63.141.144.128/28 ip4:104.195.127.0/28 ip4:3.230.26.74 ip4:3.217.56.193 ip4:52.21.127.63 ip4:3.230.59.248 ip4:34.208.121.190 ip4:54.213.31.54 ip4:44.227.88.159 ip4:34.217.199.92 ip4:4.34.42.132 ip4:4.34.42.178 ip4:4.34.42.179 ip4:213.155.74.87 ip4:213.155.74.157 ip4:213.155.74.23 ip4:213.155.74.133 ip4:3.21.23.140 ip4:3.22.102.251 ip4:3.23.36.254 ip4:3.23.38.224 ip4:3.132.65.8 ip4:3.216.57.69 ip4:3.221.39.20 ip4:23.21.137.69 ip4:34.234.250.32 ip4:44.222.17.95 ip4:52.12.139.153 ip4:52.13.73.26 ip4:52.13.126.222 ip4:54.188.101.235 ip4:54.212.187.12 ip4:147.253.221.31 ip4:156.70.17.123 ip4:156.70.17.124 ip4:156.70.17.125 ip4:156.70.17.126 ip4:156.70.17.127 ip4:164.136.252.163 ip4:14.202.162.82 ip4:148.59.100.16/28 ip4:148.59.101.16/28 ip4:138.1.36.217 ip4:147.154.18.119 ip4:149.72.251.202 ip4:149.72.63.221 ip4:35.80.141.6 ip4:44.229.121.55 ip4:148.59.100.16/28 -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.stryker.com)

Found

Record: v=DMARC1; p=quarantine; pct=100; rua=mailto:spam.dumpster@stryker.com, mailto:dmarc_agg@vali.email; ruf=mailto:spam.dumpster@stryker.com
Found at: _dmarc.stryker.com
External report address: mailto:dmarc_agg@vali.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:spam.dumpster@stryker.com, mailto:dmarc_agg@vali.email	Aggregate report addresses
ruf	mailto:spam.dumpster@stryker.com	Failure 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:spam.dumpster@stryker.com, 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: default, k1, selector1, s1, s2

Found

Selectors: default, k1, selector1, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: default, k1, selector1, s1, s2 #7

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

1024-bit DKIM key

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

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
0	stryker-com.mail.protection.outlook.com	A 52.101.10.16 A 52.101.41.4 A 52.101.194.13 A 52.101.60.179 AAAA 2a01:111:f403:f909::3 AAAA 2a01:111:f403:c927::8 AAAA 2a01:111:f403:f804:: AAAA 2a01:111:f403:c95d::	mail-bn6pr21cu00500.inbound.protection.outlook.com ✓ mail-sj2pr05cu00204.inbound.protection.outlook.com ✓ mail-ch0pr04cu00605.inbound.protection.outlook.com ✓ mail-bn3pr0301cu00103.inbound.protection.outlook.com ✓ mail-bnypr03cu00103.inbound.protection.outlook.com ✓ mail-bn3pr0301cu00200.inbound.protection.outlook.com ✓ mail-mw5pr21cu00100.inbound.protection.outlook.com ✓ mail-ph8pr05cu00300.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
stryker-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

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