> 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/forms.md).

# Forms

The Forms section provides an easy way to monitor all forms that your site is using and where that information is going.

## Use Cases

* **Ensure that forms are transmitting sensitive data over a secure connection.** We identify forms that are transmitting data like passwords, credit card numbers, and email addresses and verify that they're using HTTPS.
* **Verify that action (destination) URLs are consistent and trustworthy.** Keep track of third-party sites where form data is being sent.

## Detection

We scrape all forms found on the target along with their destination, protocol (HTTP/HTTPS), and method (GET/POST).

## Risk

Risk is assigned by verifying that forms are being submitted encrypted via HTTPS instead of a plaintext HTTP connection.

* **High** (<mark style="color:red;">●</mark> Red):
  * The page is not using HTTPS and has a password field.
  * The page is not using HTTPS and has a credit card field.
  * The form uses the HTTP GET method and has a password field.
  * The form uses the HTTP GET method and has a credit card field.
* **Medium** (<mark style="color:yellow;">●</mark> Yellow): The page is not using HTTPS and has an email address field.
* **Low** (<mark style="color:green;">●</mark> Green): No significant risks are associated with the form.

Forms rated **High** or **Medium** risk will create [issues](/docs/platform/issues.md).

{% hint style="info" %}
We recommend fixing both **High** and **Medium** risk issues.
{% endhint %}

## Monitoring

Forms can be monitored for changes by toggling their monitor status on the [List](https://app.halosecurity.com/user/security/website/script/list) page. If a change is detected it will trigger a `website-form-monitor-change` event so you can be immediately notified.

Learn more about events at:

{% content-ref url="/pages/MtggX3t55b2BwW9thVOd" %}
[Events](/docs/platform/events.md)
{% endcontent-ref %}

## Reports

* [Overview](https://app.halosecurity.com/user/security/website/form/): See risk ratings, protocols, methods, and field types (credit card/password/email) detected.
* [Summary](https://app.halosecurity.com/user/security/website/form/summary): View of field types by target.
* [List](https://app.halosecurity.com/user/security/website/form/list): List of every form detected, along with field types, method, host, and action URL. Toggle monitor status of forms.
* [Changes](https://app.halosecurity.com/user/security/website/form/changes): View changes in forms and their fields between the current and previous scans.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.halosecurity.com/docs/platform/websites/forms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.