> 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/results.md). # Reading results The `External Scan` > `Results` page gives you a score out of 100 and the list of vulnerabilities the scan detected on your assets. ## External scan score All the information gathered by the scan is aggregated and weighted into a total score out of 100. The score gives an overview of the overall risk level, calculated from all detected vulnerabilities. A score of 100/100 means the scan found nothing exploitable from the internet. Usual reasons: a small footprint (for example, just a website hosted by a provider), assets missing from your [configuration](/prevention-tools/external-scan/configuration.md), or a firewall that blocks all traffic from abroad, including the scanner in Ireland. ## Detected vulnerabilities Each vulnerability is displayed below the dashboard. You can filter vulnerabilities by criticality level (low, medium, high, or critical) to see which areas need priority attention. Once a vulnerability is fixed, it is automatically removed during the next scan.
Vulnerabilities show up while the scan is still running. Currently, it is not possible to obtain a history of addressed vulnerabilities, to export your assets, or to fetch results through an API. {% hint style="warning" %} If a vulnerability cannot be resolved immediately, take temporary measures to minimize the risk of exploitation, such as: * Applying stricter firewall rules * Implementing network segmentation You can contact our cybersecurity engineers at for advice. {% endhint %} ## Vulnerability details Click a vulnerability to open a side panel. It includes: * **Information:** the affected infrastructure component, a brief summary, the impact of the vulnerability, and remediation recommendations. * **Email exchanges:** when Stoïk SOC has communicated with your organization about a specific vulnerability (notification, follow-up, remediation guidance), the email thread is displayed directly in the panel. This section only appears when related emails exist.
If, despite the provided recommendations, you are unable to resolve the vulnerability, contact . ## Rerunning the scan If you have implemented new remediation measures, click `Rerun scan`. A scan that started before your fix can still report the vulnerability, so rerun it once the fix is in place. If a scan is cancelled, the previous results stay on screen until a new scan completes. ## Scan report Click `Scan report` to download a report in PDF format, which can be shared externally. {% hint style="info" %} To fix a finding, step-by-step hardening guides are available in cyber best practices: * [Resolve RDP service exposure](https://docs.stoik.io/cyber-best-practices/how-to-resolve-rdp-service-exposure-from-the-internet) * [Configure SPF](https://docs.stoik.io/cyber-best-practices/harden-your-environment/email-authentication/what-is-spf-and-how-do-i-configure-it) * [Configure DMARC](https://docs.stoik.io/cyber-best-practices/harden-your-environment/email-authentication/what-is-dmarc-and-how-do-i-configure-it) {% endhint %} ## Troubleshooting
A fixed vulnerability is still reported Go through this list: * **Did the scan start before the fix?** [Rerun the scan](#rerunning-the-scan). * **Is it the right port?** The vulnerability details show the exact IP or domain and port. Services often run on a non-standard port (for example, remote desktop on port 7777 instead of 3389). * **Is the website cached?** Some websites (often WordPress with a cache plugin) keep serving an old copy of their pages, which still shows old versions. Clear the cache, then rerun the scan. * **Is updating the right fix?** Some vulnerabilities are detected from how the server behaves, not from its version number. Updating does not remove them: follow the remediation in the vulnerability details. * **Is it based on a version number?** Some findings come from the version number a website displays, and websites sometimes display an outdated number. If you run a fixed version, [request an exclusion](/prevention-tools/external-scan/false-positive-vulnerabilities.md). * **Can you reproduce it?** The vulnerability details include reproduction steps your IT team can run. * **Is it really yours?** On shared hosting, a finding can belong to another website on the same server. In that case, [request an exclusion](/prevention-tools/external-scan/false-positive-vulnerabilities.md).
A vulnerability disappeared from the results Missing from one scan is not proof that it is fixed. Common reasons: * The server did not answer during the scan: it was down, slow, or your hosting provider's protection blocked part of the checks. * It was excluded: the vulnerability details show who excluded it and why (include dismissed vulnerabilities in the status filter). * The asset left the scope: a domain was removed or its DNS changed. For the same reasons, two scans of the same domain can give different results. Stoïk also improves detection regularly, so a newer scan can find more.
--- # 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/results.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.