> 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/firewalls/http-servers.md).

# HTTP Servers

HTTP servers that were detected on firewall assets.

The HTTP Servers section provides information about web servers that were detected during scanning.

## Overview

The [Overview](https://app.halosecurity.com/user/security/firewall/http/) page displays general information related to the findings, including the HTTP response codes that were observed, any redirects that were found, and the scope status of discovered hosts. You will also see any platforms, web server information, and “powered by” findings related to the servers.

## Reports

* [List](https://app.halosecurity.com/user/security/firewall/http/list): The *List* page displays detailed information per target, including any response codes that were seen and destination hosts when a redirect was encountered. Scope status is also shown, so if any redirects lead outside of your defined assets they will be correctly identified as out-of-scope.
* [Hosts](https://app.halosecurity.com/user/security/firewall/http/hosts): The *Hosts* page displays all hosts that were discovered during scanning, including out-of-scope hosts that may have been found via redirects on the web applications. If you recognize an out-of-scope host as belonging to your organization or attack surface, it’s as simple as clicking the “+” icon to add it to your scope. For in-scope hosts, the risk score is also displayed.


---

# 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/firewalls/http-servers.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.
