Skip to main content

What Are Sites?

Sites are Rafter’s live-application security monitoring feature. Instead of scanning your source code (that’s what rafter run / rafter scan do — see CLI Basics), Sites continuously monitor a live, deployed domain for:
  • Exposed backends and misconfigured services
  • DNS misconfiguration
  • SEO issues
  • Accessibility issues
Register a site once, then re-scan it any time — after a deploy, on a schedule, or before a launch.
Your API key starts with RF and should be kept secure. Never commit it to version control (e.g. GitHub). Use environment variables instead.
Sites require an API key with the read-and-scan scope to create sites or trigger scans, or the read scope to list and check them. A read-and-scan key can do both — that scope implies read.

Basic Commands

Make sure you configure an environment variable or pass in your RAFTER_API_KEY with the flag --api-key or -k (more details below).

Register a Site with rafter sites create

Registers a site and kicks off its first scan:

Re-Scan a Site with rafter sites scan

Accepts either the site’s id (from rafter sites list or rafter sites create) or its URL:

List Your Sites with rafter sites list

Check a Site’s Status with rafter sites get

Returns the site’s status, latest run, and a findings summary:

Command Reference

All rafter sites commands support:

Output Formats

Error Handling

The Sites CLI reads the actual error field from API responses rather than assuming what a status code means — this differs from rafter run’s error handling, which treats every 403 as a quota issue.

Example Workflow

API Reference

For the underlying REST API, see the Sites endpoints in the API reference.

Next Steps

CLI Basics

Learn the fundamentals of using the Rafter CLI.

Advanced CLI

Master advanced CLI features and automation.

API Reference

Build custom integrations with the REST API.

CI/CD Integration

Set up automated scanning in your pipelines.