Poor, with 3 things to fix

nexthink.cloud scored 40/100 (grade D). The main issues are no MX records and no DKIM key found for the common selectors, plus 1 more.

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

2 need attention1 failing5 for information

All checks

MXCan servers find your inbox?No MX recordsFailing

Fail: No MX records
nexthink.cloud has no MX records and no A/AAAA fallback, so it cannot receive mail, including bounces and DMARC reports. Publish an MX record pointing at your mail provider.

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 nexthink.cloud 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 nexthink.cloud.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo

Info: DMARC policy is quarantine; consider reject
Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.
How to fix this
Info: DMARC uses strict alignment
With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.

AlignmentDoes it match your From?DKIM alignment is unlikely under adkim=sNeeds attention

Warning: DKIM alignment is unlikely under adkim=s
This is a heuristic. No DKIM key was found at nexthink.cloud under the selectors we probed, and adkim=s requires the signing d= domain to equal nexthink.cloud exactly. If your mail is signed with a provider's domain or a subdomain, DKIM will not align. A key may exist under a selector we did not try; send a test message to confirm.
Info: SPF alignment is unknown
The SPF record of nexthink.cloud authorizes no sender (no +ip4, +ip6, +a, +mx, +exists or +ptr term, include of a record that has one, or +all before all), so SPF never passes and cannot align. That is correct for a domain that sends no mail; otherwise DMARC depends on DKIM alone.

BIMICan inboxes show your logo?No BIMI recordInfo

Info: No BIMI record
No BIMI record at default._bimi.nexthink.cloud. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo

Info: No MTA-STS record
No MTA-STS record at _mta-sts.nexthink.cloud. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo

Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.nexthink.cloud. 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

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing.

TypeTXT

Name / Host

_dmarc.nexthink.cloud

Some DNS providers want just “_dmarc” here.

Value

v=DMARC1; p=reject; rua=mailto:email-security@nexthink.com; adkim=s; aspf=s

Replaces

v=DMARC1; p=quarantine; rua=mailto:email-security@nexthink.com; ruf=mailto:email-security@nexthink.com; fo=1; adkim=s; aspf=s;

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to nexthink.cloud, 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.nexthink.cloud

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

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.nexthink.cloud

Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://nexthink.cloud/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.nexthink.cloud with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.