Skip to content

Scanning

Why a scan was refused

The checks that run before a scan starts and what to do about each refusal.

Before a scan starts we check, in this order: your session and multi-factor policy, the organization's status, your permission, that the asset belongs to you, that it is not blocked, that it is verified, that you have signed the authorization, that the profile is included in your plan, your plan's scan quota, that the target resolves to public addresses, the per-asset cooldown, the organization's hourly limit, any abuse suspension and scanner capacity.

The same ownership, authorization and block checks run again right before the scan is handed to a scanner, so a scan queued before a suspension or an expired verification fails instead of running.

Common reasons and fixes

What you seeWhat it meansWhat to do
Re-verification requiredVerification expired or the token was no longer foundPublish the token again and press Check verification.
Target changedThe asset now resolves to new addresses and we are re-checkingWait about a minute and try again.
Authorization neededYou have not signed the current authorizationSign the record from the asset page.
Profile not in your planStandard or Deep need a higher planUpgrade or use Quick.
Quota used upYou reached your plan's scan allowanceWait for the next period or upgrade.
CooldownThe asset was scanned within the last 10 minutesTry again shortly.
Rate limit30 scans started in the last hourTry again later.
Asset pausedYou are over the asset limit of your planRemove assets or upgrade. See Cancel, resume and the Free plan.
Asset blockedTasScan has blocked the assetContact support.
Target not publicThe address is private, loopback or a cloud-metadata addressOnly public targets can be scanned.
Target not allowedThe address belongs to TasScan itselfThese cannot be scanned.