When merchants look for a way to block Tor exit nodes and anonymous proxies on Shopify, they are usually dealing with a familiar pattern in their order logs: a fraudulent transaction where Shopify’s native Fraud Analysis flags an anonymous proxy or high-risk IP connection after payment is captured, or a wave of anonymous sessions probing checkout forms and scraping product catalogs.
While the Tor network and proxy relays have legitimate privacy uses, they also give bad actors a low-cost way to hide their network origin, rotate IP addresses between attempts, and evade single-IP blacklists. Because Shopify hosts your storefront on a managed global CDN without access to edge firewall files like .htaccess or Nginx configs, you need a layered approach to filter anonymous traffic.
In this guide, we explain how Tor exit nodes and different proxy types work, what LabX Fraud Filter detects at the network level, and how to combine storefront Tor, ASN, and IP rules with server-side Checkout Protection so you stop abuse without locking out real buyers. For a complete overview of visitor filtering across all rule dimensions, see our Shopify traffic and bot blocking guide.
Why do fraudsters use Tor exit nodes and anonymous proxies on Shopify?
As the Tor Project Abuse FAQ explains, the Tor network routes an encrypted connection through three volunteer relays—an entry guard, a middle relay, and finally an exit node that forwards traffic to the public web. When someone visits your Shopify store using Tor Browser or a script routed through the Tor SOCKS proxy, your store never sees the visitor’s original IP address; it only sees the public IP of the exit relay.
Alongside Tor, attackers route traffic through open HTTP/SOCKS proxies, commercial proxy-hosting providers, and residential proxy networks to mask high-risk activity:
- Anonymous checkout probing and card testing: Fraudsters use Tor exit nodes or rotating proxy pools to test stolen payment cards without exposing their home ISP or country (see our guide to stopping card testing attacks on Shopify).
- Evading single-IP blocks: Because a Tor circuit periodically rotates to a different exit node—and proxy scripts cycle through subnets—blocking one individual IP address after a bad order rarely stops the next attempt.
- Bypassing regional restrictions: Attackers in unsupported regions use anonymous relays located in your domestic market to browse restricted collections or probe regional pricing.
- Catalog and price scraping: Automated spy tools route requests through proxy servers hosted on virtual private servers (VPS) and bare-metal hosting networks to scrape product handles and inventory counts.
Although Shopify’s built-in Fraud Analysis evaluates IP reputation and proxy indicators, those warnings only appear on the order timeline after checkout is complete—leaving you with non-refundable payment processing fees even when you cancel the order.
How do Tor exit nodes, hosting proxies, and residential proxies differ?
Not all proxy and anonymity connections look the same on the wire. Effective filtering on Shopify starts with distinguishing what can be identified reliably by IP and Autonomous System Number (ASN) from what requires checkout validation:
| Traffic Type | Network-Layer Signature | Primary Ecommerce Risk | How LabX Fraud Filter Handles It |
|---|---|---|---|
| Tor exit nodes | Public IP addresses published on the Tor Bulk Exit List | Anonymous fraud probing, policy evasion, and scripted abuse | Blocked on the storefront via Block Tor traffic in Settings > Mitigator (refreshed weekly) |
| Datacenter & hosting proxies | Rented servers on cloud, VPS, and hosting ASNs (M247 AS9009, BuyVM AS53667, Datacamp AS60068, AWS AS16509, DigitalOcean AS14061, Hetzner AS24940) | Automated catalog scrapers, headless browsers, and bulk proxy pools | Blocked via Block datacenter traffic or custom ASN rules in Blocking Rules > ISP (see our datacenter vs VPN blocking guide) |
| Known static proxy IPs & subnets | Specific IPv4/IPv6 addresses or /24–/64 blocks logged in past fraud attempts | Repeat manual fraudsters or dedicated proxy exit servers | Blocked via exact IP, prefix, range, or CIDR rules in Blocking Rules > IP Address (see our Shopify IP and CIDR blocking guide) |
| Residential proxies & consumer VPNs | Consumer ISP connections (home broadband or mobile carrier networks) | Privacy-conscious buyers; occasionally used by human fraudsters to disguise location | Allowed on the storefront to avoid false positives; enforced at checkout via server-side Checkout Protection |
How does LabX Fraud Filter detect Tor exit nodes and proxy networks?
We believe merchants deserve plain facts about how IP and proxy detection works under the hood—and what its boundaries are.
When a visitor lands on your storefront and you have location, ISP, Tor, or datacenter rules enabled, the Fraud Guard theme app embed makes one signed GeoIP lookup per browsing session via the Shopify App Proxy (/apps/fraud/geo) and caches the result in sessionStorage for 30 minutes.
On our server, that lookup checks the visitor’s real client IP (read from the X-Forwarded-For header that Shopify sets on App Proxy requests, which cannot be forged by a client header) against two datasets preloaded into memory at startup:
- Weekly Tor exit-node snapshot (
Block Tor traffic): Our server checks the visitor’s IP against a preloaded set of published Tor exit-node addresses so the check completes well within the storefront’s 800 ms fetch budget. As stated in our product documentation, the Tor list is a weekly refreshed snapshot—an exit node that joined the Tor network after the most recent weekly refresh is not on the list until the next update. - Curated hosting and proxy-adjacent ASNs (
Block datacenter traffic): Using MaxMindGeoLite2-ASN, our server checks whether the visitor’s ASN belongs to cloud compute, VPS, bare-metal, and anonymity-adjacent hosting providers frequently rented for proxy exits and bot automation (including AWS, Google Cloud, Azure, DigitalOcean, Hetzner, OVH, Vultr, Linode/Akamai, Contabo, ColoCrossing, FranTech/BuyVM, M247, Datacamp/CDN77, Leaseweb, Hostinger, Clouvider, and Alexhost). We call this datacenter blocking, not VPN blocking, because a shopper using a consumer VPN on a residential network is not blocked. - Fail-open resilience: If our server is unreachable, the lookup times out after 800 ms, or an IP cannot be resolved, LabX Fraud Filter fails open and lets the visitor through rather than locking real customers out.
How do you set up Tor and proxy blocking on your Shopify storefront?
You can enable automatic Tor, datacenter, and bot filtering in Settings > Mitigator, add targeted proxy ASNs or IP subnets in Blocking Rules, and customize what blocked visitors see. Follow along with screenshots in our bot and content protection guide.
Step 1: Copy your Admin access link before testing
Before turning on Tor, ISP, or IP rules—especially if you test your storefront using a privacy browser or corporate proxy—open Settings > General settings and copy your Admin access link (https://your-store.myshopify.com/?fg_bypass=...). Open that URL once in your browser so our server verifies your bypass token and stores it in your browser, letting you skip every storefront rule while testing. Clicking Generate new link invalidates the old token immediately (see our block page and admin bypass guide).
Step 2: Turn on Block Tor traffic and bot switches in Mitigator
In the LabX Fraud Filter admin, go to Settings and select the Mitigator tab:
- Toggle on
Block Tor traffic: Blocks visitors connecting from IP addresses on our weekly refreshed Tor exit-node list. - Toggle on
Block datacenter traffic: Blocks connections originating from cloud, VPS, and server-hosting ASNs where commercial proxy pools and automated scrapers run. - Toggle on
Auto-block unknown botsandAuto-block suspicious crawlers: Stops scripted HTTP clients (curl/,wget,python-requests,python-urllib,go-http-client,okhttp,puppeteer,playwright,selenium,headlesschrome,phantomjs) and headless browser anomalies (navigator.webdriver, or simultaneous zero plugins, zero touch points, and zero languages). - Keep
Allowed bot list(Allow verified good bots) enabled: Storefront rules evaluate in strict precedence order:Admin bypass→Allowed bot list (25 crawlers)→Explicit Allow rules→Auto-block unknown bots→Block Tor / Block datacenter traffic→Suspicious crawler checks→Country Block-all-except→Redirect rules→Block rules→Allow by default. Because the Allowed bot list runs at step 2, verified crawlers like Googlebot, AdsBot-Google, Bingbot, Applebot, Facebookbot, GPTBot, ClaudeBot, AhrefsBot, and SemrushBot are never blocked (matching Google Search Central’s crawler guidelines).
Step 3: Block specific proxy ASNs or high-risk IP subnets
When you spot a specific proxy provider or abusive IP block in your order logs:
- Block by ASN or ISP name (
Blocking Rules > ISP): Click the quick-add datacenter buttons (+ DigitalOcean (AS14061),+ Amazon Web Services (AWS) (AS16509),+ Hetzner Online (AS24940),+ Google Cloud (AS15169),+ Linode / Akamai (AS63949),+ OVHcloud (AS16276)) or enter any comma-separated ASN (AS9009,AS60068) or provider name substring (M247,Datacamp,Leaseweb). - Block by IP, range, or CIDR (
Blocking Rules > IP Address): Block exact IPv4/IPv6 addresses, leading prefixes (IP Start With), inclusive IP ranges, or CIDR subnets manually or via CSV upload up to 2,000 lines (see our IP and location rules documentation). Click the+ Known VPN / Proxy exit IPquick-note chip to record why the rule was created. - Customize your block page (
Settings > Blocking template): Using one of our six customizable block page templates, display your store logo, brand colors, and a clear message asking any legitimate privacy-minded shopper on Tor Browser to switch to a standard connection.
Why must you pair storefront Tor blocking with server-side Checkout Protection?
Being transparent about how Shopify apps work is essential for your store’s defense (which we compare in detail in our storefront vs checkout blocking guide).
Storefront rules in LabX Fraud Filter run in the visitor’s browser via the Fraud Guard theme app embed. That creates two important limitations when dealing with Tor and anonymous proxies:
- Tor Browser’s “Safest” mode and scripted bots disable JavaScript: Tor Browser includes a security slider whose “Safest” level disables JavaScript across all sites by default. Likewise, automated card-testing bots fetch pages with
curlor call Shopify’s Cart and Checkout APIs directly without running browser scripts. When JavaScript is off, no storefront app embed can execute in the browser. - Residential proxies look like normal home connections: If a fraudster routes through a residential proxy or consumer VPN, their IP belongs to a normal consumer ISP rather than a Tor exit node or datacenter ASN.
To stop orders at the payment gate regardless of browser settings or proxy type, pair storefront rules with server-side Shopify fraud prevention using Checkout Protection (see our Checkout Protection setup guide). Powered by a native Shopify Cart and Checkout Validation Function, Checkout Protection executes on Shopify’s servers and cannot be bypassed by disabling JavaScript or calling Cart APIs directly:
| Anonymous Fraud Scenario | Why Storefront Tor / IP Blocking Alone Misses It | Server-Side Checkout Protection Rule to Enforce |
|---|---|---|
| Tor Browser user on “Safest” mode (JS disabled) using a throwaway email | Storefront JavaScript does not run when the browser disables scripts | Condition: Email (Contains) — block disposable email domains (@mailinator.com, @tempmail.com, @guerrillamail.com, @10minutemail.com, @dispostable.com, @yopmail.com, @trashmail.com, @getairmail.com) on Shopify’s servers |
| Fraudster using an anonymous proxy to ship to a restricted country or ZIP | Proxy exit node masks the visitor’s browsing country on the storefront | Condition: Country or Zip — block checkout server-side when the shipping address matches an unsupported country or high-risk postal code |
| Attacker routing through a residential proxy to a known reshipper | Residential proxy IP belongs to a consumer ISP, bypassing Tor and datacenter filters | Condition: Address (Contains) and Phone — block known freight-forwarder street strings and burner phone numbers (matched by digits regardless of formatting) |
| Repeat offender rotating Tor circuits on every checkout attempt | Each new Tor circuit exits from a different relay IP address | Condition: Name, Email (Exact match), or Customer tag — block the buyer’s recipient name, email, or tagged account across all attempts |
Note that if you also enable right-click, keyboard shortcut, or text-selection blocking in Settings > Content protection, those settings act only as a casual copy deterrent in the browser—they cannot stop OS screenshots, curl, or DevTools.
Once your rules are active, open Analytics and Visitor in LabX Fraud Filter (covered in our Analytics and Visitor log guide) to monitor how many visits were stopped by Tor exit node, Datacenter IP, or custom Rule match: ip / Rule match: isp rules over the past 7, 30, or 90 days, and inspect the 50 most recent blocked or redirected visits.
Frequently asked questions
How does LabX Fraud Filter detect Tor exit nodes on Shopify?
When you enable Block Tor traffic in Settings > Mitigator, LabX Fraud Filter checks the visitor IP address on the server against a weekly refreshed snapshot of the Tor Project exit-node list. The lookup runs once per browsing session via the Shopify App Proxy and is cached in the browser for 30 minutes.
What happens if a Tor Browser user disables JavaScript?
Storefront blocking runs in the visitor browser via the Fraud Guard theme app embed. Because Tor Browser in its Safest security mode disables JavaScript by default, a visitor with scripts turned off can still view storefront HTML. To stop orders from being placed at checkout, pair storefront rules with server-side Checkout Protection, which runs on Shopify servers and cannot be bypassed.
Does blocking Tor and datacenter traffic also block residential proxies or consumer VPNs?
No. Block Tor traffic only matches published Tor exit nodes, and Block datacenter traffic matches cloud, VPS, and hosting ASNs. Connections routed through residential ISPs—including consumer privacy VPNs and residential proxy networks—are not blocked by those switches, which keeps normal shoppers from being locked out.
Will enabling Tor and proxy blocking hurt my Google SEO rankings?
Not when Allow verified good bots remains enabled. LabX Fraud Filter evaluates its built-in allowlist of 25 search engine, social media, AI, SEO, and archive crawlers at the very top of the precedence order before checking Tor, datacenter, ISP, or IP block rules.
Sources
Part of our guide: Traffic & bot blocking →