> 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/frequently-asked-questions.md). # Frequently Asked Questions Find answers to common questions about SHELLZERO X, website security scans, vulnerability findings, security agents, and platform capabilities. *** ### General Questions #### What is SHELLZERO X? SHELLZERO X is a cybersecurity platform focused on website and domain security assessment, vulnerability intelligence, and security monitoring. It helps users identify potential weaknesses in publicly observable systems. #### What can SHELLZERO X check? Published scanning capabilities include SSL/TLS configuration, HTTP security headers, exposed software versions, known vulnerabilities, DNS and email security records, subdomains, blacklists, website reachability, response time, IP ownership, and CDN/WAF indicators. The exact checks available may depend on the target and the platform's current functionality. #### Who should use SHELLZERO X? SHELLZERO X is intended for website owners, developers, security professionals, and organizations seeking visibility into potential website and domain security issues. Users must have appropriate authorization before assessing a system. ### Scanning and Results #### How do I run a scan? Open the scanning functionality available on the platform, enter the target domain or website as requested, complete any required verification, and submit the scan. Review the resulting report when processing is complete. The available steps may vary depending on the platform interface and the type of assessment. #### Does a scan guarantee that my website is secure? No. Automated scanning can identify potential issues, but it cannot guarantee that a website is free from vulnerabilities. Some weaknesses may not be externally visible or detectable by the available checks. #### Why does a scan report a vulnerability? A finding may be based on detected software information, known vulnerability data, configuration indicators, or other available evidence. Review the finding details and validate that the issue applies to your environment before taking action. #### Can scan results contain false positives? Yes. A reported issue may not apply to the target's actual configuration. Validate findings against reliable technical documentation and the affected system before implementing changes. #### Why are some issues not detected? The relevant information may not be publicly available, the check may not cover the affected component, or the issue may require authenticated or deeper testing. A clean report does not establish that every component is secure. ### Domain Verification and DNS #### Why might domain verification be required? Certain additional checks may require confirmation that you control the domain. Follow the verification instructions presented by the platform. #### Which DNS and email security records are relevant? Common checks include: * **SPF:** Identifies the mail servers authorized to send email for a domain. * **DKIM:** Uses cryptographic signatures to help verify email authenticity and integrity. * **DMARC:** Defines how receiving mail servers should handle messages that fail authentication checks and supports reporting. * **DNSSEC:** Helps protect DNS data integrity through cryptographic validation. * **CAA:** Specifies which certificate authorities may issue certificates for a domain. Correct configuration depends on the domain's infrastructure and operational requirements. ### Security Agents #### What are Sentinel and Hunter? Sentinel is associated with asset monitoring, while Hunter focuses on exploited vulnerability intelligence. Both are identified as running agents in the published platform information. Their precise scope and availability should be confirmed through the current platform interface and official announcements. #### Are Guardian, Patch, and Chain available? These agents have been identified as in development. * **Guardian:** Associated with firewall and WAF defense workflows. * **Patch:** Associated with remediation guidance. * **Chain:** Associated with Web3 security monitoring. Do not assume that their planned capabilities are available for general use until officially released. ### Monitoring and Notifications #### Does SHELLZERO X support Telegram alerts? Telegram alerts are included in the platform's published information. The available setup process, supported event types, and notification conditions should be confirmed through the current platform interface. #### Will every finding generate an alert? Not necessarily. Notifications may depend on the available monitoring features, configuration, and event conditions. A scan result should not be assumed to trigger an alert automatically. ### Security and Responsible Use #### Can I scan any website? Only scan websites and systems you own or are explicitly authorized to assess. A website being publicly accessible does not automatically authorize security testing. #### Should I fix every finding immediately? Prioritize findings based on their validated severity, potential impact, exposure, and relevance to your environment. Some findings may require further investigation before remediation. #### Is SHELLZERO X a replacement for a security team or penetration test? No. Automated scanning can support security operations, but it does not replace comprehensive security reviews, appropriate penetration testing, secure development practices, or incident response. ### Getting Help #### What should I do if a scan fails? Check the target address, review any displayed error message, confirm whether verification is required, and retry if appropriate. For persistent issues, provide the error details and relevant context to support. #### How can I contact SHELLZERO X support? Email [**dev@shellzerox.org**](mailto:dev@shellzerox.org) with a description of the issue, the affected feature, any relevant error messages, and the steps you have already tried. Do not include passwords, private keys, recovery phrases, or authentication tokens in support requests. ### Final Note SHELLZERO X capabilities and agent availability may evolve as the platform develops. For functionality-specific questions, rely on the current platform interface and official announcements rather than assuming that planned features are already available. --- # 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/frequently-asked-questions.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.