> For the complete documentation index, see [llms.txt](https://docs.transparentedge.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.transparentedge.eu/security/waf/waf-false-positive-reporting.md).
# WAF False Positive Reporting
The WAF is designed to protect your website from malicious traffic. However, under certain circumstances, it may inadvertently block legitimate traffic.
The false positives report allows you to identify these cases and fine-tune the WAF configuration to act with greater precision, ensuring your website remains protected without impacting trusted traffic.
### How to request the report
Navigate to the WAF section within Analytics and click the Request Report button located at the top of the page. Once opened, define the analysis period, up to a maximum of 7 days.
To generate a more detailed report, this tool allows you to apply a site filter. By selecting one or more sites, the system will limit the analysis and report generation exclusively to those specific sites. This filter is optional: if no site is selected, the report will automatically be generated using data from all sites associated with the company.
If you have whitelists configured and wish to verify whether any of the IPs included in them have been blocked during the specified period, select the relevant whitelists in the form prior to submitting the request.
Once all fields have been completed, click the Request Report button. The report will be delivered to your email inbox within a few minutes, listing the affected IPs.
---
# 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.transparentedge.eu/security/waf/waf-false-positive-reporting.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.
