There are 44 detector categories. Each can be enabled or disabled per
engagement:
redactproxy rules disable india_pii.pan # one subcategory
redactproxy rules disable india_pii # every subcategory under it
redactproxy rules enable india_pii.pan
The authoritative list for the build you are running is
redactproxy rules show, which prints exactly these descriptions from
the same source. This page is that list, grouped.
Warning
The four allowlist.* categories work backwards from the rest.
Disabling one makes more get redacted, not less. See
The allowlist categories below.
Out-of-band/security-testing callback services (burpcollaborator.net, interact.sh, webhook.site, etc.); these are the tester’s OWN tooling, never the client’s.
allowlist.third_party_saas
Specific third-party vendor products a client’s own site actively integrates with (razorpay.com, zoho.in, engati.ai, etc.); see wellknown.go’s thirdPartySaaSDomains for the full list. This is a weaker judgment call than the other allowlist categories, since seeing one of these does reveal something about the client’s tech stack, just not the client’s identity. It is its own toggleable category for exactly that reason.
allowlist.web_infrastructure
Common third-party CDN/font/analytics/widget hosts (jsdelivr.net, googletagmanager.com, clarity.ms, recaptcha.net, etc.); these are embedded on almost any scanned website, client’s or not, and carry no client-identifying information in the hostname itself. See wellknown.go’s webInfrastructureDomains for the full list and what is deliberately excluded (customer-subdomain SaaS platforms like Zendesk and Okta, where the hostname itself is often the finding).
allowlist.wellknown_platforms
Well-known public dev platforms (github.com, npmjs.com, pastebin.com, stackoverflow.com, etc.); see wellknown.go’s wellKnownPlatformDomains for the full list.
These four are exceptions, not detectors. They stop values from being
redacted, so disabling one means more gets redacted, not less.
They exist because it is genuinely useful for Claude to recognize
infrastructure that carries no client identity: that a domain is GitHub
and it can therefore use the gh CLI, that a hostname is Google Tag
Manager rather than client infrastructure, that a callback domain is
Burp Collaborator and therefore your own tooling, likely an SSRF or RCE
test. Tokenize those and Claude loses context it would otherwise have
for free.
Most engagements should leave all four enabled. The one worth
considering individually is allowlist.third_party_saas, since a vendor
domain does fingerprint the client’s tech stack even though it does not
name the client. Disable that one alone on an engagement where even
that should stay hidden:
Some things are excluded on purpose, because a detector that fires on
innocent text costs more than one that misses an edge case:
Bare apex domains on file-extension TLDs (.do, .ai, .rs,
.sh, .py). main.rs and logo.ai are far more often filenames.
Use rules block --domain for these.
Reserved and documentation values.example.com, RFC 5737
documentation IP ranges and similar are excluded, since they are not
client data and tokenizing them just adds noise.
Names and prose, which have no shape at all. Use rules block.