> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/code-scanning/miscellaneous/scanning-frequencies.md).
# Scheduled Scan Frequencies
Aikido provides default scanning frequencies for various components to ensure security and performance. Here, you'll learn about these scanning defaults and how to change them.
{% hint style="info" %}
Aikido also runs in real time in the IDE on every save, and on every push or pull request via PR gating. The settings below control the scheduled re-scan that runs in addition.
{% endhint %}
### Scanning Frequencies
* By default, for all paid plans, Aikido does **daily** scans for open-source dependencies, SAST, IaC, secrets, cloud, containers, and Front-End Domains.
* Domains scanned with Hosted Domains and APIs are by default done **twice a week** as this has a higher load on your system.
* In case you quickly want to verify whether a fix was implemented correctly, you can trigger a **manual scan** by clicking 'Start Scan' in the UI.
> Workspaces on a free plan are scanned every 3 days, and users cannot trigger scans manually. Hosted domains are scanned once a week.
### Changing Scanning Frequency
In case you want to change your scanning frequency, you can do this by going to [General Settings](https://app.aikido.dev/settings/account) (admins only) and click **Change Scanning Frequency**.
---
# 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://help.aikido.dev/code-scanning/miscellaneous/scanning-frequencies.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.