> For the complete documentation index, see [llms.txt](https://docs.oshi.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oshi.co/help-and-support/staying-safe.md).

# Staying Safe

Protect yourself from scams and impersonators. Verify official Oshi accounts, spot fake links, and keep your account secure.

How to verify official Oshi channels and protect yourself from scams.

***

### Official domains

> ⚠️ **Only trust these domains.** Anything else claiming to be Oshi is fake.

| Brand    | Official Domain                                                              |
| -------- | ---------------------------------------------------------------------------- |
| Oshi     | [**oshi.co**](http://oshi.co)                                                |
| GATE 2   | [**gate2.co**](http://gate2.co) (also [gate2.oshi.co](http://gate2.oshi.co)) |
| MahoSeka | [**mahoseka.com**](http://mahoseka.com)                                      |

***

### Oshi will never:

* Ask for your password or login credentials via email or DM
* Request direct crypto transfers outside official websites
* Contact you through unofficial Discord servers
* Ask you to click links in unsolicited messages
* Pressure you to act urgently or "miss out"

***

### Common scams

**Fake social accounts**

Scammers create accounts that look official. Always verify handles match our Official Links exactly.

**Phishing emails**

Emails from domains other than [oshi.co](http://oshi.co), [gate2.co](http://gate2.co), or [mahoseka.com](http://mahoseka.com) are not from us. Check the sender address, not just the display name.

**Unofficial Discord servers**

Our only official Discord is [discord.gg/oshi](http://discord.gg/oshi). If you're unsure whether a server is legitimate, ask in the official Discord or contact <support@oshi.co>.

**"Support" DMs**

Oshi staff will never DM you first asking for account info or payments. We recommend turning off DMs from unknown users in Discord, and never accepting requests from anyone claiming to be part of the Oshi team.

**Too-good-to-be-true offers**

Free rewards, exclusive airdrops, or special deals outside official channels are scams.

***

### When in doubt

> 📝 **Don't click or respond.** Reach out to <support@oshi.co> to verify before taking any action.

You can also ask in our Discord. The moderation team can help verify if something is legitimate.

***

**Related articles**

* [Official Links](https://docs.oshi.co/start-here/official-links.md): All official websites and social channels
* [Managing Your Account](https://docs.oshi.co/help-and-support/managing-your-account.md): Account security best practices
* [Support Channels](https://docs.oshi.co/help-and-support/support-channels.md): Where to get help

{% hint style="info" %}
**Still need help?** Join our [Discord](https://discord.gg/oshi) or email <support@oshi.co>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.oshi.co/help-and-support/staying-safe.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
