> For the complete documentation index, see [llms.txt](https://docs.adsecure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adsecure.com/faqs/detections.md).

# Detections

Find here frequently asked questions about detections

## What is a violation?

A violation corresponds to a type of detection, which can be malicious, non-compliant, or provide a negative user experience. Check all violations in our [Detections](/docs/detections.md) section to consult the complete list of violations AdSecure supports.

## Which types of violations does AdSecure detect?

AdSecure detects many different types of violations across the categories of user security, user experience and user advisory. A description per violation can be found [here](/docs/detections.md).

| User Security violations          | User Experience violations | User Advisory violations |
| --------------------------------- | -------------------------- | ------------------------ |
| Adware                            | Auto-download              | IAB: Ad Dimension        |
| Browser Locker                    | Auto-redirect              | IAB: Ad File Compression |
| Drive-by mining                   | Auto-redirect App Store    | IAB: Ad Request Count    |
| Malicious URL: Google Webrisk     | Auto-vibrate               | IAB: Ad Weight           |
| Malicious URL: Sucuri             | Back Button Hijack         | Suspicious TLD           |
| Malicious URL: Virustotal         | JS Alert on entry          | Threat Intelligence      |
| Malware                           | JS Alert on exit           | Unsafe content: Adult    |
| Phishing URL: Google Webrisk      | Landing Page Error         | Unsafe content: Medical  |
| Ransomware                        | Permission: Camera         | Unsafe content: Racy     |
| Scareware                         | Permission: Clipboard      | Unsafe content: Spoof    |
| SSL non-compliant                 | Permission: Geolocation    | Unsafe content: Violence |
| Unwanted Programs: Google Webrisk | Permission: Microphone     |                          |
|                                   | Permission: Notification   |                          |
|                                   | Uncommon Protocols         |                          |

## Can I choose which violations to be alerted on?

Yes, by creating an [Alert Rule](/adsecure-documentation/how-to-guides/alert-rules.md). An Alert Rule lets you define which violations you want to be alerted for upon detection. Detection of these alerts will be highlighted in color in reports, and can also be used to generate [notifications](/adsecure-documentation/how-to-guides/manage-notifications.md) (in-app notifications, emails, callback URL).

## Can you whitelist URLs in AdSecure?

In AdSecure it’s possible to make an exception for a certain domain and/or alert violation, to temporarily not be taken into account when you check the compliance of ads or site pages. A good example of this would be when you are in the process of resolving a known threat or quality issue detected on a project that scans frequently.

Applying an [Allowlist Rule](/adsecure-documentation/how-to-guides/allowlist-rules.md) in such a case will allow you to save time to focus on new alert violations that may occur on the project, rather than having to repeatedly check alerts on the known issue you are in the process of resolving.

## Do you check against Anti Virus providers?

AdSecure is integrated with VirusTotal, Sucuri and Google Safe Browsing.


---

# 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.adsecure.com/faqs/detections.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.