> For the complete documentation index, see [llms.txt](https://shellzerox.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shellzerox.gitbook.io/docs/support-and-faq/contact-and-support.md). # Contact & Support Learn how to contact SHELLZERO X for platform assistance, technical issues, and questions about security scanning. *** ### Overview SHELLZERO X provides a contact channel for questions and issues related to the platform. When requesting assistance, provide clear information about the problem so it can be reviewed efficiently. ### Support Contact For assistance, contact SHELLZERO X by email. | Contact Method | Details | | ------------------ | -------------------------- | | Support Email | | | Official Website | | | Official X Account | | ### When to Contact Support Contact support if you experience issues such as: * Problems accessing your account. * Scan submission or completion failures. * Domain verification difficulties. * Unexpected or incomplete scan results. * Questions about currently available platform features. * Issues with monitoring or notification functionality. * Suspected platform errors or technical problems. Before contacting support, review the relevant troubleshooting guidance and collect any available error details. ### What to Include in Your Request To help explain the issue, include the following information where relevant: | Detail | What to Provide | | ------------------- | ----------------------------------------------------------------------------- | | Subject | A concise summary of the issue. | | Affected Feature | The page, scanning function, verification process, or other feature involved. | | Description | What happened and what you expected to happen. | | Error Details | The exact error message, if available. | | Time | The approximate date and time of the issue. | | Steps Taken | Any troubleshooting steps you have already completed. | | Supporting Evidence | Relevant screenshots with sensitive information removed. | Share only the information necessary to explain the issue. If a domain or scan report is involved, confirm that you are authorized to share its details. ### Protect Your Account and Information When requesting assistance: * Never share your password. * Never disclose private keys or wallet recovery phrases. * Do not send authentication tokens or other credentials. * Remove sensitive information from screenshots and attachments. * Verify that you are using the official contact details listed on this page. Support requests should not require you to disclose wallet recovery phrases or private keys. ### Reporting a Security Concern If you identify a potential security issue affecting SHELLZERO X, provide a concise description of the suspected vulnerability and any relevant evidence that can be shared safely. Avoid exploiting the issue, accessing unrelated data, or disrupting platform services to demonstrate its impact. Do not include sensitive credentials or unnecessary personal information in your report. ### Before Sending Your Request Confirm that your message includes a clear description of the issue, the relevant feature, and any error details needed to understand the problem. For questions about planned functionality, specify the feature you are asking about so its current availability can be clarified. --- # 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://shellzerox.gitbook.io/docs/support-and-faq/contact-and-support.md?ask=&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.