> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/prevention-tools/external-scan/configuration.md). # Configuration Add your domain names and public IP addresses so the External Scan covers your whole perimeter. You can add assets one by one, or import a long list at once. ## Prerequisites * At least one domain name, or confirmation that you have none. * At least one public IP address, or confirmation that you have none. ## Configuration status Some incidents handled by Stoïk CERT could have been avoided if public IP addresses other than those associated with the domains had been provided. The External Scan is therefore listed as `Not configured` until both prerequisites are met.

To configure the External Scan, go to `External Scan` > `Settings`. ## Adding assets ### Adding assets one by one

On the Domains or IP addresses card, click `Add` and type the domain name or IP address you want to include. The asset is validated and added to your scan perimeter immediately. Also add the domain names that you do not use or that you purchased as extras. Attackers may target them too, particularly for impersonation or malicious use. ### Importing in bulk

If you have a long list of domains or IP addresses, you can import up to 500 entries in a single batch. 1. Go to `External Scan` > `Settings`, then click `Import in bulk` on the Domains or IP addresses card. 2. Paste your list in the text area, one entry per line. Copy-pasting a column directly from Excel or a CSV works as-is. 3. Check each line, which is validated in real time: * : valid entry, will be submitted. * : invalid format, must be removed. * The counters under the field show how many entries are valid vs invalid. 4. Click `Import`. ### Reading the import summary After you submit, a summary screen breaks down the result into three groups: * **Added**: entries accepted and immediately included in your scan perimeter. They will appear in the next External Scan run. * **Pending**: entries received but flagged for manual review by the Stoïk SOC. This typically happens for domains with a high internet reputation, where we double-check that you actually own or are entitled to scan them. They are added to the scan perimeter once approved. * **Rejected**: entries refused. The most common reasons are: * already in your perimeter (duplicate); * on Stoïk's blacklist (e.g. public services we never scan); * invalid format on the server side. Close the modal once you have reviewed the summary. To import another batch, reopen `Import in bulk`. ## Good to know * Results remain visible even if only domains or IP addresses are entered. Warning banners prompt you (on Stoïk Protect and in the monthly summary) to complete the setup. * The External Scan can also be run on IP addresses only. * If you purchased your cyber insurance policy via a questionnaire, the IP addresses entered in the questionnaire are automatically imported into Stoïk Protect. * If you don't have an additional domain name or IP address, check that your infrastructure has no domain name or public IP address. This prevents unnecessary reminders. * You can only add the domains or IP addresses of a company you are acquiring with a written agreement from that company, together with the list of its assets. Contact . --- # 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.stoik.io/prevention-tools/external-scan/configuration.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.