CLI

The Norcube CLI (norcube, alias nrc) exposes DomainRadar under the nrc domainradar command group: live checks, bulk checks you can stream or export, saved domains, brand monitoring and the name generator. Every flag of every command is in the generated CLI reference.

Every command supports --org <slug>, --profile <name>, -o table|json|yaml|text and --query (see output and scripting). Setup is the standard CLI login:

nrc login
nrc org use <slug>
nrc domainradar check example.com     # sanity check

Checks count towards your DomainRadar usage exactly as in the dashboard: each one is billed by the method that answered it, and cached answers are free (see check modes).

Check domains

nrc domainradar check acme.io acme.dev acme.app
nrc domainradar check --file names.txt --mode info -o json
cat names.txt | nrc domainradar check - -o text --query "[?available].domain"

# accept a cached answer up to a day old (free)
nrc domainradar check acme.io --max-age 24h

--mode is bloom, verified (the default), info or full, the same check modes as the dashboard. Domains come from the arguments, a file (--file) or standard input (--file - or a single -), one per line; blank lines, # comments and duplicates are skipped. check takes up to 100 domains at a time; for more, use a bulk check.

Bulk checks

# start a bulk check of up to 100,000 domains
nrc domainradar bulk create --file names.txt --mode bloom
nrc domainradar bulk create acme.io acme.dev --wait      # wait for it to finish

# follow it: results print as the server produces them
nrc domainradar bulk watch <job-id>

nrc domainradar bulk list
nrc domainradar bulk get <job-id>
nrc domainradar bulk results <job-id> --available --tld com,io

# the whole result set as a file (CSV from the server, or JSON)
nrc domainradar bulk export <job-id>                      # bulk-check-<job-id>.csv
nrc domainradar bulk export <job-id> --format json --to results.json
nrc domainradar bulk export <job-id> --to - | head

nrc domainradar bulk cancel <job-id>   # results so far are kept (and billed)
nrc domainradar bulk delete <job-id>   # --yes in scripts

bulk watch reconnects on its own when the connection drops and never prints a result twice; Ctrl-C stops watching, not the job. With -o json or -o yaml it prints the final list of results instead of streaming. bulk export refuses to overwrite an existing file.

With --wait, bulk create waits for the job to finish and prints it again. If the job failed or was cancelled, the command exits 1 with the error code job_failed (the job is under details in the JSON error), so a script can't mistake it for a finished check. CLI versions before 0.20 exited 0 there. Ctrl-C stops waiting, not the job; --wait-timeout (default 1 hour) gives up waiting with exit code 7.

Saved domains

nrc domainradar saved list --available
nrc domainradar saved list --sort expiry_date -o json --query "[].domain"
nrc domainradar saved add acme.io --notes "ask legal first"
nrc domainradar saved remove acme.io

See saved domains for what the watchlist keeps.

Brand monitoring

nrc domainradar watchers create acme --allow acme.com,acme.io --min-score 60 --notify security@acme.com
nrc domainradar watchers list
nrc domainradar watchers update <watcher-id> --disable
nrc domainradar watchers delete <watcher-id>

nrc domainradar hits list --watcher <watcher-id> --min-score 70
nrc domainradar hits get <hit-id>

watchers also answers to brand-watchers, and hits to brand-hits. How watchers, scores and alerts work is covered in brand monitoring.

Name generator

nrc domainradar names generate "invoicing for freelancers" --category fintech --size small --wait
nrc domainradar names list
nrc domainradar names results <job-id> --max-length 8 --sort length

# check chosen names as domains: every name in every TLD, as a bulk check
nrc domainradar names results <job-id> --max-length 6 -o text --query "[].name" \
  | nrc domainradar names check <job-id> --file - --tld com,io --wait

names check starts an ordinary bulk check, so bulk watch and bulk results work on it. names generate --wait and names check --wait follow the same rule as bulk create --wait: a failed or cancelled job exits 1 (job_failed). See name generator.

CI tokens

A CI token with the domainradar.check scope can run check and bulk create and read every list. Changing saved domains, brand watchers, bulk jobs and name generation needs a signed-in user (nrc login); a CI token gets 403 INSUFFICIENT_SCOPE (exit code 5).

Related

• Check modes, bulk checks
• MCP tools for AI agents
• nrc api domainradar ... for any endpoint without a command