> 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/security-scanning/website-and-domain-security.md).

# Website & Domain Security

Understand how SHELLZERO X evaluates publicly observable website and domain security configurations.

***

### Overview

Website and domain security involves multiple layers, including encrypted connections, browser security controls, domain configuration, and publicly exposed infrastructure.

SHELLZERO X assesses selected aspects of these layers through passive security checks, helping users identify potential weaknesses in their external security posture.

### Website Security Checks

| Security Area         | What Is Examined                                                                  | Why It Matters                                                                       |
| --------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| SSL/TLS Certificates  | Certificate validity, hostname matching, and related configuration.               | Helps identify issues that could undermine secure connections.                       |
| TLS Configuration     | Supported protocol versions and related encryption settings.                      | Outdated or weak configurations can reduce connection security.                      |
| HTTP Security Headers | Headers associated with browser security protections.                             | Missing or misconfigured headers may leave websites more exposed to certain attacks. |
| Website Reachability  | Response behavior, redirects, and availability.                                   | Helps identify accessibility issues and understand the public-facing endpoint.       |
| CDN and WAF Detection | Observable indicators of content delivery networks and web application firewalls. | Provides context about the infrastructure protecting or delivering a website.        |

### Domain Security Checks

Domain-level checks examine publicly available records and information associated with a domain.

| Security Area        | What Is Examined                                   | Why It Matters                                                        |
| -------------------- | -------------------------------------------------- | --------------------------------------------------------------------- |
| DNS Configuration    | Relevant DNS records and configuration indicators. | Incorrect or weak configurations may affect reliability and security. |
| Email Authentication | SPF, DKIM, and DMARC records where detectable.     | These mechanisms help reduce ema                                      |


---

# 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/security-scanning/website-and-domain-security.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.
