A failed scan usually means Probe could not reach or evaluate the submitted public URL. It does not always mean your app is broken or insecure.
Probe needs a public web URL that can be reached by an outside request. It cannot scan private localhost pages, password-protected dashboards, internal VPN routes, or apps that block the scanner before public pages load.
Common failure reasons
› The URL has a typo or unsupported scheme.
› The app is behind login, basic auth, VPN, IP allowlisting, or a coming-soon gate.
› The deployment is asleep, expired, deleted, or still building.
› The page returns too many redirects, a hard error, or a bot-blocking challenge.
› The domain has DNS, TLS, or certificate issues.
› The app blocks normal public requests from the scanner.
› Probe had a temporary worker or network failure.
What to try first
Open the URL in a private browser window. If you cannot reach a public page without signing in, Probe probably cannot scan it either.
Check that the URL starts with https:// and points to the deployed app, not an internal dashboard, admin panel, localhost address, or private preview that requires team access.
If the app uses a protection layer, allow normal public access to the page you want scanned, then run Probe again.
If you paid and the report failed
If Stripe payment succeeded but the scan failed, report access broke, or no findings rendered because of a product failure, email support@runprobe.com with the checkout email, submitted URL, and report link if available.
Support can investigate the scan and either help restore access, offer a re-run, or review refund eligibility under the refund policy.
Do not send dashboard credentials, private keys, source code, or provider tokens. Probe support does not need them for normal scan troubleshooting.