Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Running scans

Running scans

How long does a scan take?

Quick answer

A typical scan of a small app takes roughly an hour, according to the in-app Documentation. Larger apps take longer, and rate limits can slow a scan further. Open the running scan from Recent Scans to see its current phase. Slow does not mean failed.

The short version

A scan of a small app usually takes about an hour. That figure comes from the in-app Documentation page. Bigger codebases and apps with many pages take longer. In the scan list we captured, finished scans ran from about an hour and a half to about two and a half hours.

You do not need to stay on the page, because the run is durable and carries on if you close the tab, lose your connection or head home for the day. Check back later.

How it works in Cyberlop

Every scan moves through five phases. Each phase builds on the one before it, so the total time is the sum of all five.

PhaseWhat happens
1. Pre-reconOne agent reads the cloned repository and maps the frameworks, entry points and data flows.
2. ReconAn agent maps the live app into a sitemap of endpoints.
3. Vulnerability analysisEight specialists analyse the code in parallel, each in its own lane.
4. ExploitationAgents try to prove each hypothesis with a real browser. You can turn this phase off.
5. ReportingA final agent assembles the report from confirmed findings.

Phase 3 runs its specialists side by side to keep a thorough scan fast. If your profile has Run exploitation phase switched off, the scan skips phase 4.

Rate limits from the AI provider can add waiting time, and Cyberlop handles them by retrying with growing pauses, then picking the work up again once the limit clears. The scan gets slower. It does not fail.

What to do next

Full tutorial

How to run a pentest scan in Cyberlop, and what happens next

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.