Mail domain report: sentinelone.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:mail.zendesk.com include:mktomail.com include:_spf.salesforce.com include:_spf.atlassian.net ip4:35.80.141.6/32 ip4:44.229.121.55/32 ip4:208.185.235.0/24 ip4:148.59.108.0/23 ip4:148.59.106.0/23 ip4:10.183.25.18/32 ip4:10.176.20.243/32 ip4:10.226.205.244/32 ip4:35.91.229.248/32 ip4:35.162.29.198 ip4:44.234.245.33/32 ip4:100.20.176.7/32 ip4:54.152.14.251/32 ip4:54.173.58.140/32 ip4:52.204.40.143/32 ip4:54.84.4.28/32 ip4:35.173.106.12/32 ip4:54.156.212.29/32 ip4:18.184.189.217/32 ip4:18.197.77.147/32 ip4:18.184.105.23/32 ip4:18.185.165.73/32 ip4:18.185.181.167/32 ip4:18.195.130.52/32 ip4:172.27.0.101 ip4:10.192.91.198 ip4:54.77.246.118/32 ip4:52.215.76.168/32 ip4:52.208.90.157/32 ip4:159.183.71.12/32 ip4:198.244.59.30/32 ip4:198.244.59.33/32 ip4:198.244.59.35/32 ip4:167.89.97.235 ip4:168.245.34.51 ip4:43.228.187.74/32 ip4:43.228.185.67/32 ip4:149.72.214.81/32 ip4:168.245.40.122/32 ip4:54.240.116.11/32 ip4:54.240.116.27/32 ip4:76.223.147.27/32 ip4:76.223.147.28/32 ip4:76.223.147.29/32 ip4:76.223.147.31/32 ip4:76.223.147.32/32 ip4:76.223.147.33/32 ip4:76.223.147.34/32 ip4:76.223.147.35/32 ip4:76.223.147.36/32 ip4:76.223.147.37/32 ip4:76.223.147.38/32 ip4:76.223.147.39/32 ip4:76.223.147.40/32 ip4:76.223.147.41/32 ip4:76.223.147.42/32 ip4:76.223.147.43/32 ip4:76.223.147.44/32 ip4:76.223.147.45/32 ip4:76.223.147.46/32 ip4:76.223.147.47/32 ip4:76.223.147.48/32 ip4:76.223.147.49/32 ip4:76.223.147.50/32 ip4:54.160.246.246/32 ip4:54.237.141.197/32 ip4:52.20.211.99/32 ip4:34.197.67.5/32 ip4:44.194.118.42/32 -all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 7 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

pass

p=reject (_dmarc.sentinelone.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:92bb588df3a54eb395ce31486c2a35ea@dmarc-reports.cloudflare.net,mailto:dmarc@sentinelone.com,mailto:dmarc_agg@vali.email
Found at: _dmarc.sentinelone.com
External report address: mailto:92bb588df3a54eb395ce31486c2a35ea@dmarc-reports.cloudflare.net (authorized)
External report address: mailto:dmarc_agg@vali.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:92bb588df3a54eb395ce31486c2a35ea@dmarc-reports.cloudflare.net,mailto:dmarc@sentinelone.com,mailto:dmarc_agg@vali.email	Aggregate 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:92bb588df3a54eb395ce31486c2a35ea@dmarc-reports.cloudflare.net, mailto:dmarc@sentinelone.com, mailto:dmarc_agg@vali.email
✓ Subdomain policy: reject #20

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

Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: google

Found

Selectors: google
_domainkey: NOERROR

Selector	Key	Flags
google	RSA 2048 bits

Checks

✓ Keys found: google #7

DKIM keys found for this domain with selectors: google
✓ Strong keys #23

DKIM keys are strong enough: google: RSA 2048 bits.
✓ 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

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
10	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
20	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
30	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
40	aspmx2.googlemail.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
50	aspmx3.googlemail.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓

Checks

✓ 5 MX records #9

Found 5 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.
✓ Redundant MX hosts #12

Found 5 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 5 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
aspmx2.googlemail.com	none	-
aspmx3.googlemail.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