Certain IP addresses
Match visitors whose public IP address exactly matches an address on a merchant-entered list.
Certain IP addresses matches a visitor based on their exact public IP address against a list you enter. It's a good fit for gating content to a known, fixed set of locations — for example, letting only your office or warehouse network see an internal catalog or a testing page.
This rule matches exact public IP addresses only; IP ranges, CIDR blocks (such as 192.168.1.0/24), and wildcards are not supported. Enter each address separately, and update the list if your network uses a changing IP address.
Like most access rules (aside from the action-based ones such as Passcode, Secret link, Subscribe, and Confirmation prompt), Certain IP addresses can be set to match If the visitor's IP is on your list, or Unless it is — inverting it to match every other IP instead. See Combining rules.
Add the rule
Open Locks and create a new lock, or open an existing one to edit it.
Choose the content you want to protect. See Access rules overview for how rules fit into a lock.
Click the Unlock rules tab, then in the Condition type dropdown, select Certain IP addresses.

Enter the exact public IP address(es) you want to match. You can add more than one.

Choose If or Unless.
Click Save.
Example: Limit an internal price list to the office network
Suppose the office's fixed public IP address is 203.0.113.10, and only visitors using that network should see an internal price list.
Select the Internal price list page as the content to protect.

Add Certain IP addresses, choose If, and enter
203.0.113.10. Click Add IP address to turn it into a chip — the value isn't saved until you do.

Leave the rule's Redirect URL empty.
Set the Access denied message to:
This page is only available when you’re connected to an approved network.

Click Save.
Result on the storefront
A visitor whose public IP is exactly 203.0.113.10 can open the page. Any other IP address fails the rule and sees the message above. If the office's public IP changes, update the value in the rule before access can work again.

Related docs
Last updated
Was this helpful?