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

# Features

### IOC Parser

* Extract Indicators of Compromise (IOCs) from a variety of sources such as - Security Blogs, PDF Reports, CSV, Text Files, Zipped Files, Raw Text dump, JSON text, etc.
* Supports extracting a variety of IOCs such as - ASN, BITCOIN\_ADDRESS, CVE, DOMAIN, EMAIL, FILE\_HASH\_MD5, FILE\_HASH\_SHA1 , FILE\_HASH\_SHA256, IPv4, IPv6, MAC\_ADDRESS, MITRE\_ATT\&CK, URL, YARA\_RULE.
* Supports extraction of defanged IOCs.
* Supports multiple Encoding Types.
* Supports extracting of Metadata.
* Supports default WHITELIST.

### IOC Sources

***WIP -*** Ingest aggregated Sources to understand what kinds of attacks are trending in the wild.

### IOC Intel

***WIP -*** Ingest extra Intel about IOCs to gain a deeper understanding about the threats.


---

# 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:

```
GET https://docs.iocparser.com/features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.