> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/platform/websites.md). # Websites Information about web servers that were identified. The [Websites section](https://app.halosecurity.com/user/security/website/summary/) contains all of the web-related data observed while crawling targets that have accessible web servers. This data is monitored for changes and scanned for malware and phishing links, along with other common risks. Assets that are discovered on out-of-scope hosts are also listed, allowing you to add these hosts as Targets. The website scan is non-invasive and crawls the website cataloging assets and connections. It is included with the base target scan. The [Summary](https://app.halosecurity.com/user/security/website/summary/) view provides a single pane listing of all findings across the various types of assets, along with their risk scores and hosts they were identified on. {% hint style="info" %} Many parts of the Website section scan elements for Malware, Phishing, and Adult content. We use third-party services, such as [Google WebRisk](https://cloud.google.com/web-risk/docs/detect-malicious-urls) and [Phishtank](https://www.phishtank.com/), to flag this content based on the host or URL. {% endhint %} ## Elements The website scan helps you catalog and monitor the following types of elements: * [**Certificates**](/docs/platform/websites/certificates.md): TLS certificates that are in use and any data associated with them, including common name, subject alternative name, expiration, and any TLS protocol versions and ciphers that are offered. * [**Scripts**](/docs/platform/websites/scripts.md): Javascript that is loaded on any Targets, including third-party scripts. * [**Cookies**](/docs/platform/websites/cookies.md): Cookies that have been set, along with their attributes and expiration dates. * [**Headers**](/docs/platform/websites/headers.md): HTTP response headers that were observed and any platforms or software products that are associated with them. * [**Forms**](/docs/platform/websites/forms.md): Forms are listed with their destination host, and those that submit sensitive information like credit card numbers, passwords, and emails are identified. * [**Links**](/docs/platform/websites/links.md): Any links that are found on your websites are scanned for malware for phishing content, and their response codes are checked to determine broken links. * [**Downloads**](/docs/platform/websites/downloads.md): Similar to what we do with links, downloads are scanned for any malicious content and can be monitored by their file type and where they are hosted. * [**Traffic Hosts**](/docs/platform/websites/traffic-hosts.md): All hosts that are observed sending traffic while rendering your website are recorded here. * [**Meta Tags**](/docs/platform/websites/meta-tags.md): Meta tags embed descriptive information about your websites and are used for various purposes such as SEO and directing the behavior of web crawlers. We extract meta tags during the crawling process. * [**Pages**](/docs/platform/websites/pages.md): Pages are generated based on the URLs that are discovered during the crawling process. ## Scan Details By default website scans are set to crawl the site for: * Up to 3 hours or 10,000 total pages. * They do not access pages that require a login or authentication. * The IP addresses of the scanner are… {% hint style="warning" %} The crawler can be blocked by a Web Application Firewall (WAF). If we detect this, we'll create an issue to alert you. {% 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.halosecurity.com/docs/platform/websites.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.