> 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/use-cases/changelog.md). # Changelog ## 0.2.3 - 2021-09-01 ### Changed * **UI** - Copying IOCs from UI will switch between CSV and JSON depending on the type of text copied. * **UI** - Formatting change in . * **UI** - Handling redirect URLs, so 404 are handled correctly. ## 0.2.2 - 2021-07-11 ### Fixed * **API** - Fixed /twitter API. ## 0.2.1 - 2021-07-09 ### Added * **API** - Support for parsing IOCs from gzip files. ### Fixed * **API** - Fixed handling of incorrect URL returning 500 Error. ## 0.2.0 - 2020-06-22 ### Added * **API** - Support for more defang patterns. ### Fixed * **API** - Fixed empty response issue. ## 0.1.9 - 2020-05-26 ### Added * Support for extracting IOCs from Twitter Profiles with /twitter API ## 0.1.8 - 2020-05-21 ### Added * Support for more defang patterns. ### Changed * Updated dependencies. ## 0.1.7 - 2020-05-19 ### Added * Support for "application/zip" Content-Type to handle extracting IOCs from zipped files. ## 0.1.6 - 2020-05-18 ### Fixed * Incorrect MITRE\_ATT\&CK regex fixed. ### Changed * Improvements to Parse API. ## 0.1.5 - 2020-05-10 ### Changed * Fixed preprocessing PDF text. * Tweaked EMAIL IOC regex. ## 0.1.4 - 2020-05-06 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Changed * Bug fixes and improvements to Parse API ## 0.1.3 - 2020-05-05 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * Support for more Content-Type added. ## 0.1.2 - 2020-04-29 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * Support for parsing PDFs and extracting IOCs from it. ## 0.1.1 - 2020-04-20 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * Support for more Content-Type added. ## 0.1.0 - 2020-04-15 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * IOC Type - MAC\_ADDRESS ## 0.0.9 - 2020-04-14 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * /text and /raw API for parsing IOCs from a text dump. ## 0.0.8 - 2020-04-13 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * "public" parameter added for /url API. This should be useful if anyone doesn't want their searches being used in any other APIs. ## 0.0.7 - 2020-04-12 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * Caching to improve speed of response. ### Changed * DOMAIN parsing improvement by cross referencing parsed data with a list of TLDs from ICANN () ## 0.0.6 - 2020-04-08 ### Fixed * Incorrect EMAIL Addresses being parsed. ### Added * /url will return a new key - "meta" describing the source. ## 0.0.5 - 2020-04-07 ### Changed * HTML Processing. * Better config management. * Timeout Increased. ### Added * Better POST API Schema validation. * Support for ASN IOC. ## 0.0.4 - 2020-04-05 ### Changed * Status API response. ### Added * Support for BITCOIN\_ADDRESS IOC. ## 0.0.3 - 2020-04-05 ### Fixed * Catastrophic Backtracking problem for IPv4. * Added request headers to help parse some sites. * Better handling of encoding types. ### Changed * Directory structure for handling post operations. ### Added * Better response status codes - 200, 204, 400, 502. --- # 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/use-cases/changelog.md?ask= ``` 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.