Skip to main content
This page lists every field recognised in config.json. Fields marked required have no default and must be set before verifyngo will start. All duration values use Go’s duration string format: "30s", "10m", "2h", "168h" (7 days).

Core


IP Trust


Paths

Default bypass_paths list When bypass_paths is not set in config.json, verifyngo uses the following patterns:

CAPTCHA

Provider selection

cap (self-hosted Cap)

turnstile (Cloudflare Turnstile)

hcaptcha


Walk-away & Ban

Walk-away tracking counts how many times a visitor abandons the challenge page without solving it. When the threshold is exceeded the visitor is banned.

Progressive

Progressive mode observes traffic passively on specified paths before deciding to challenge. Visitors who exceed max_requests within request_window are challenged.

Store

The store holds ban state, walk-away counters, and progressive counters.

store.file (file backend)

store.redis (Redis backend)


ASN

ASN lookups power policy-file rules that match on autonomous system numbers or organisation names.

AbuseIPDB

When enabled, verifyngo reports banned IPs to AbuseIPDB after they have been banned a configurable number of times.

Branding

All branding fields are optional. They customise the appearance of the challenge page shown to visitors. Default branding.details_text