Target QCDR Rules and Tokens by IP Address, Range, or CIDR

Max and All Access can restrict a Rule or Token by the current client IP. QCDR accepts IPv4 and IPv6 single addresses, CIDR networks, and explicit start-to-end ranges, with one shared Include or Exclude behavior for the list.

Configure IP Targeting

  1. Edit the Rule or Token.
  2. Open IP targeting.
  3. Choose Include only listed IPs or Exclude listed IPs.
  4. Enter one item per line.
  5. Save and test from a request whose client IP you can verify.

Supported Entry Formats

  • Single IPv4: 192.0.2.30
  • IPv4 CIDR: 198.51.100.0/24
  • IPv6 CIDR: 2001:db8::/32
  • Explicit range: 203.0.113.10 - 203.0.113.50

QCDR validates addresses and CIDR prefixes when the item is saved. An explicit range cannot mix IPv4 and IPv6 endpoints.

Include vs. Exclude

With Include only listed IPs, the Rule or Token is eligible only when the client matches at least one entry. With Exclude listed IPs, a matching client is blocked and every other valid client IP passes this gate.

If the list is empty, IP targeting adds no restriction.

Sites Behind a Proxy or CDN

IP targeting is only as accurate as QCDR’s resolved client IP. By default QCDR trusts the direct connection address. It considers X-Forwarded-For only when the direct connection comes from a configured trusted proxy address or CIDR. Configure that trust boundary before diagnosing an IP rule on a proxied site.

Caching Can Defeat the Intended Audience

A full-page cache or CDN that serves one visitor’s already-transformed HTML to another can undermine IP-specific output. Review cache variation/bypass behavior before using IP targeting for content that must differ reliably by requester.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.