Skip to main content

Frequently asked questions

Discovery and scanning​

How long does a first scan take?​

The first results, such as resolved domains and open ports, usually appear within minutes. A complete picture takes longer: port scans, screenshots and discovery jobs run in the background, and Red Kite keeps discovering new resources over the following days. See My first scan.

Red Kite found resources that are not mine. Is that normal?​

Yes. Discovery follows links between resources, and some of them lead to shared or third-party infrastructure, such as a CDN or a hosting provider. Each resource has a confidence score that tells how likely it is to be yours. Block the resources that are not yours: they will be hidden and no longer scanned.

Why is a resource not being scanned?​

Red Kite only runs its automation on resources that are not blocked and that have a confidence score of 50 or more, or that are verified. If a resource that belongs to you is marked as unlikely, verify it.

Should I delete or block a resource that is not mine?​

Block it. A deleted resource is recreated if Red Kite finds it again, while a blocked resource is remembered and ignored. Delete a resource only when it does not exist anymore. See Data enrichment.

Why does the same website appear several times?​

Red Kite creates a website for every combination of domain, IP, port and path it finds, to catch virtual hosts serving different content. Merge the duplicates. See Website duplicates.

Can I re-scan a resource right away?​

Yes. Go to Automation > Launch and run the job you need on the resource. See Launching a job.

Does Red Kite scan more than what I gave it?​

Red Kite starts from your seed data and follows what it finds: the IPs your domains resolve to, the subdomains of your domains, the hosts in your IP ranges, and so on. It does not scan arbitrary targets. Use blocking to stop it from following leads that are not yours.

Intel​

What is the difference between a finding and an intel?​

A finding is a piece of information found by a job, such as an open port or a service name. An intel is an issue detected on a resource, such as an exposed database, with a severity and recommendations.

I fixed an issue. Why is the intel still open?​

Intel statuses are managed by your team: Red Kite does not close an intel on its own. Move it to Ready to retest, re-scan the resource, then move it to Resolved. If the issue comes back later, Red Kite reopens it as a Regression. See Managing intel.

Can I create my own intel?​

Yes. Any filter can become an intel. See Configuring intel.

Access and collaboration​

How do I give someone access to only one project?​

Add them to a group that is restricted to that project, such as the default project read-only or project contributor groups. See Inviting teammates.

Can I share results with someone who does not have an account?​

Yes. A project can be shared with a link, in view-only or editable mode. See Working with teammates.

Can I use Red Kite from my own scripts?​

Yes. Everything in the interface is available through the API, with an API key.

Getting help​

Can't find your answer? Contact the Red Kite team.