From e8f10fb2db87a4ccdc20e3a5e2743e72bfa75b47 Mon Sep 17 00:00:00 2001 From: Ryan Dewhurst Date: Mon, 1 Feb 2021 13:32:38 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f883b7ff..1d1862ef 100644 --- a/README.md +++ b/README.md @@ -89,7 +89,7 @@ The DB is located at ~/.wpscan/db The WPScan CLI tool uses the [WordPress Vulnerability Database API](https://wpscan.com/api) to retrieve WordPress vulnerability data in real time. For WPScan to retrieve the vulnerability data an API token must be supplied via the `--api-token` option, or via a configuration file, as discussed below. An API token can be obtained by registering an account on [WPScan.com](https://wpscan.com/register). -Up to 25 API requests per day are given free of charge, that should be suitable to scan most WordPress websites at least once. When the daily 25 API requests are exhausted, WPScan will continue to work as normal but without any vulnerability data. Users can upgrade to paid API usage to increase their API limits within their user profile on [WPScan.com](https://wpscan.com/). +Up to 25 API requests per day are given free of charge, that should be suitable to scan most WordPress websites at least once per day. When the daily 25 API requests are exhausted, WPScan will continue to work as normal but without any vulnerability data. Users can upgrade to paid API usage to increase their API limits within their user profile on [WPScan.com](https://wpscan.com/). #### The Free plan allows 25 API requests per day. View the different [available API plans](https://wpscan.com/api).