Skip to content
ADLER

Quickstart

For operators · running scans

Tutorial

Your first scan

Section titled “Your first scan”

After installing, scan one username across the embedded registry:

Terminal window
adler torvalds

The text view streams Found and Uncertain rows as they resolve. NotFound rows are hidden by default — pass --all to include them, or pipe to jq for a machine-readable list:

Terminal window
adler --format ndjson torvalds | jq -r 'select(.kind == "found") | .url'

Logging

Section titled “Logging”

Adler’s tracing output is gated by the ADLER_LOG env var (defaults to adler=info):

Terminal window
ADLER_LOG=adler=debug adler torvalds

Common next steps

Section titled “Common next steps”
  • Filter to specific sites or tags — adler --tag dev --only git scans only dev-tagged sites whose name contains git. See Usage → Filtering.
  • Output as JSON / CSV / HTML — adler --format json torvalds > out.json, --format csv, or --format html for a self-contained report. See Usage → Output.
  • Use the web UI — adler --web boots a SolidJS SPA at http://127.0.0.1:8080 with live SSE streaming, history, side-by-side diff, and a read-only access-engine view. See Web UI.
  • Scan many usernames — adler --input users.txt runs through a list, grouped output. See Usage → Batch & enrichment.
  • Watch for changes — adler --watch torvalds diffs against the last run and reports new / removed accounts.

When something looks off

Section titled “When something looks off”

A whole-registry scan from a fresh datacenter IP often returns a lot of Uncertain rows — that’s not Adler “not working”, that’s the CDN edge mass-banning the IP range. See FAQ → Why is everything coming back as Uncertain? for the residential-IP / browser-backend remedies.

For sites that always return Uncertain because they sit behind Cloudflare / a TLS-fingerprint check / a login wall, see Access engine — that’s the whole point of the engine.