Excellent: no problems found

skyhigh.cloud scored 100/100 (grade A). No problems were found in the checks that ran. Detected senders: Google Workspace.

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

4 passed0 failing4 for informationDetected senders: Google Workspace

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?DKIM key publishedPass

Pass: DKIM key published
skyhigh.cloud publishes a DKIM key under google.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No BIMI recordInfo

Info: No BIMI record
No BIMI record at default._bimi.skyhigh.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.skyhigh.cloud. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this

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

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

Publish the MTA-STS recordTXT

Tells sending servers that skyhigh.cloud publishes an MTA-STS policy at https://mta-sts.skyhigh.cloud/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.skyhigh.cloud

Some DNS providers want just “_mta-sts” here.

Value

v=STSv1; id=202610040209

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.skyhigh.cloud. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location

https://mta-sts.skyhigh.cloud/.well-known/mta-sts.txt

Contents

version: STSv1
mode: testing
mx: primary.us.email.fireeyecloud.com
mx: alt1.us.email.fireeyecloud.com
mx: alt2.us.email.fireeyecloud.com
mx: alt3.us.email.fireeyecloud.com
max_age: 604800

Set up a TLS report addressinstruction

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

Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@skyhigh.cloud, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.skyhigh.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.skyhigh.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://skyhigh.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.skyhigh.cloud with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.