sentinelone.net

sentinelone.net · Last checked 2026-10-04 02:20 UTC

sentinelone.net

Good, with 4 things to fix

sentinelone.net scored 80/100 (grade B). The main issues are no DKIM key found for the common selectors and external DMARC report address is not authorized, plus 4 more. Detected senders: Google Workspace and Amazon SES.

Checked 2026-10-04 02:20 UTC · fresh check

2 passed4 need attention0 failing2 for informationDetected senders: Google Workspace, Amazon SES

Diagnosis notes

  • Warning: DNS lookup budget exhausted

    This diagnosis stopped sending DNS queries after 150 queries. Checks that needed more lookups report their remaining results as unknown; the domain's records may be unusually large or slow to answer.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF ends in softfail (~all)Info
  • Info: SPF ends in softfail (~all)

    "~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
  • Warning: No DKIM key found for the common selectors

    None of the 47 selectors probed under sentinelone.net publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for sentinelone.net.

  • Warning: Some DKIM lookups failed

    6 of 47 selector lookups under sentinelone.net returned TIMEOUT, so whether those selectors hold a key is unknown. Try again later; if it persists, check the domain's nameservers.

DMARCWhat happens to fakes?External DMARC report address is not authorizedNeeds attention
  • Warning: External DMARC report address is not authorized

    Reports go to sentinelone.com, which is outside sentinelone.net. RFC 7489 requires that domain to publish a valid v=DMARC1 TXT record at sentinelone.net._report._dmarc.sentinelone.com; without it receivers will not send you aggregate reports. Your report provider normally publishes this for you.

AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?Could not look up the BIMI recordNeeds attention
  • Warning: Could not look up the BIMI record

    The TXT query for default._bimi.sentinelone.net returned TIMEOUT, so BIMI status is unknown. Try again later.

MTA-STSIs mail to you encrypted?Could not look up the MTA-STS recordNeeds attention
  • Warning: Could not look up the MTA-STS record

    The TXT query for _mta-sts.sentinelone.net returned TIMEOUT, so MTA-STS status is unknown. Try again later.

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.sentinelone.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

How to fix it

Enable DKIM for Google Workspaceinstruction

Google Workspace generates the DKIM key for each account, so the exact record must come from Google Workspace. Without DKIM, mail it sends for sentinelone.net cannot pass DMARC through DKIM.

Applies to: google._domainkey.sentinelone.net

  1. In Google Workspace, enable DKIM signing for sentinelone.net: Generate the key in Admin console > Apps > Gmail > Authenticate email, then publish the TXT record shown there. Publish exactly the record Google Workspace shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://support.google.com/a/answer/174124

Enable DKIM for Amazon SESinstruction

Amazon SES generates the DKIM key for each account, so the exact record must come from Amazon SES. Without DKIM, mail it sends for sentinelone.net cannot pass DMARC through DKIM.

Applies to: _domainkey.sentinelone.net

  1. In Amazon SES, enable DKIM signing for sentinelone.net: account-specific: copy the CNAME/TXT from the Amazon SES dashboard. Publish exactly the record Amazon SES shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dkim-easy.html

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to sentinelone.net, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.sentinelone.net

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@sentinelone.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.sentinelone.net with the value v=TLSRPTv1; rua=mailto:<that address>.