> 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/docs/threat-intelligence/introduction.md).

# Introduction

## What is Threat Intelligence?

Threat Intelligence is a service that provides insight regarding a specific URL's violation activity. This service will provide an indication on a scale from 0 to 5 of how risky you can consider the URL is.

The risk is an estimation AdSecure gives about the probability and the severity of violations. The higher the risk is, the more probable it is that the URL will present violations. The less the risk is, the safer it can be considered.

You can consider the risk an implementation of the [Overall Risk of Symantec](https://www.symantec.com/content/en/us/about/media/securityintelligence/SSR-Severity-Assesment.pdf). The severity from 1 to 5 (0 being nonexistent) is defined as:

1. Very low
2. Low
3. Moderate
4. Severe
5. Very severe

> Threat intelligence is a service built on [Odin](/docs/threat-intelligence/odin.md).

## What can I use it for?

You may use Threat Intelligence as a filter, in order to optimize the distribution of scans in an effective way. As it does not consume scans, you may check beforehand whether an analysis is required or not. This decision could be based on how risky Threat Intelligence considers the domain or the existence of specific violations.

## We're here to help!

For support requests, bug reports or if you need to discuss a private concern, please contact [AdSecure support directly](https://www.adsecure.com/contact-us).


---

# 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/docs/threat-intelligence/introduction.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.