When merchants search for how to block VPN and datacenter traffic on Shopify, they are usually reacting to a sudden spike in automated abuse: competitor spy tools scraping product catalogs, headless browsers skewing conversion analytics, or waves of bots testing stolen credit cards at checkout. In response, many store owners look for an aggressive “block all VPNs and proxies” switch.
However, treating every VPN, proxy, and cloud server IP as the same threat creates two problems at once. First, blanket VPN claims can cause false positives when legitimate shoppers browse from corporate networks, privacy services, or mobile carrier relays—while still failing to catch bots that skip the browser. Second, most automated storefront abuse does not come from consumer privacy apps at all; it originates from rented cloud servers and virtual private servers (VPS) running in commercial datacenters.
In this guide, we explain the network-level difference between datacenter IPs and consumer VPNs on Shopify, why we name our control datacenter blocking rather than VPN blocking, and how to combine storefront ASN, Tor, and bot filtering with server-side checkout rules in LabX Fraud Filter. For a complete overview of visitor filtering, see our Shopify traffic and bot blocking guide.
What is the difference between a datacenter IP and a consumer VPN on Shopify?
Every IP address on the internet belongs to an Autonomous System Number (ASN) and an organization name—the network operator or Internet Service Provider (ISP) responsible for routing that block of addresses. When a visitor loads your Shopify store, looking up their IP in an ASN database reveals what kind of network they are connecting from:
- Consumer broadband and mobile carrier ISPs: Real shoppers browsing from home Wi-Fi or cellular data connect through consumer telecom networks (for example, Comcast, AT&T, Deutsche Telekom, or BT).
- Datacenter and cloud hosting ASNs: Cloud infrastructure providers, VPS hosts, and bare-metal server farms—such as Amazon Web Services (
AS16509,AS14618), DigitalOcean (AS14061), Google Cloud (AS15169), Microsoft Azure (AS8075), Hetzner Online (AS24940), OVHcloud (AS16276), and Linode / Akamai (AS63949)—lease virtual machines to developers and automated scripts. Real consumers do not browse retail stores from a headless Linux server inside an AWS or DigitalOcean data center. - Tor exit nodes: The Tor network routes encrypted traffic through relays before exiting to the public web via a published list of exit nodes. Tor exit nodes are frequently used to mask automated probing and fraudulent checkout attempts.
- Consumer and residential VPNs: Privacy-conscious shoppers, remote employees, and travelers often use commercial VPN clients on their laptops or phones. Many consumer VPN connections route through consumer-facing network ranges or residential ISP pools rather than cloud-compute ASNs.
| Traffic Source | Typical Network / ASN Type | Primary Shopify Merchant Risk | Recommended Action in LabX Fraud Filter |
|---|---|---|---|
| Cloud & VPS servers (AWS, DigitalOcean, Hetzner, OVH) | Hosting & compute ASNs (AS16509, AS14061, AS24940, AS16276) | Automated catalog scrapers, price spy tools, headless browsers, and card testing attacks | Block on storefront via Block datacenter traffic switch or custom ISP rules |
| Tor network | Published Tor Project exit-node IP addresses | Anonymous fraud probing, credential stuffing, and policy evasion | Block on storefront via Block Tor traffic switch (refreshed weekly) |
| Headless browsers & scripted clients | Any network, identifiable by curl, python-requests, puppeteer, or navigator.webdriver | Automated scraping, inventory hoarding, and fake newsletter signups | Block via Auto-block unknown bots and Auto-block suspicious crawlers |
| Consumer / residential VPNs | Consumer ISPs or residential proxy pools | Often legitimate privacy-conscious buyers; occasionally used by human fraudsters to mask location | Allow storefront browsing; enforce server-side Checkout Protection on order fields |
Why does LabX call it datacenter blocking instead of VPN blocking?
We believe merchants deserve plain, accurate descriptions of what security tools actually detect. In LabX Fraud Filter, the setting in Settings > Mitigator is named Block datacenter traffic—not “VPN blocker”—for a specific technical reason.
Automated fraud and scraping require cheap, high-bandwidth compute. When an attacker launches a script to test stolen credit cards or scrape every product handle on your store, they spin up instances on cloud and VPS providers like AWS, Google Cloud, Azure, Alibaba Cloud, Tencent Cloud, DigitalOcean, Hetzner, OVH, Vultr, Linode, Contabo, ColoCrossing, M247, Leaseweb, or Hostinger.
LabX Fraud Filter identifies those connections on the server using MaxMind GeoLite2-ASN lookups matched against a curated set of cloud, VPS, bare-metal, and hosting ASNs. When Block datacenter traffic is enabled, visitors arriving from those server networks are blocked automatically.
By contrast, a normal shopper using a consumer VPN usually appears on a consumer or residential network and is not blocked by the datacenter toggle. We would rather name the signal we actually detect—hosting providers where automated bots live—than promise blanket VPN detection and lock paying customers out of your storefront.
Why can storefront network rules alone never stop every bot?
Understanding where each rule executes on Shopify is critical before you design your defense strategy. Because Shopify hosts your storefront on its global CDN, Shopify delivers the initial page HTML to the visitor’s browser before any third-party app script runs:
- Storefront rules run in the visitor’s browser: Storefront blocking in LabX Fraud Filter works through the Fraud Guard theme app embed. When a browser loads your page, the embed evaluates your ruleset and either displays your custom block page or redirects the visitor. However, a technical attacker or custom script that disables JavaScript, fetches pages using
curlwithout executing scripts, or sends HTTP requests directly to Shopify’s Cart and Checkout APIs can bypass browser-level blocking. No Shopify app can intercept raw HTTP requests at the CDN edge before the page reaches the browser. - Checkout Protection runs on Shopify’s servers: To stop bots and human fraudsters that bypass the browser—or that route through residential VPNs where the IP looks like a normal home connection—you need Shopify fraud prevention at checkout. LabX Fraud Filter’s Checkout Protection compiles your checkout rules into a native Shopify Cart and Checkout Validation Function that runs server-side on Shopify’s own infrastructure. Even if JavaScript is turned off or a script calls the Cart API directly, Shopify enforces your checkout rules on the server before payment can be submitted, so they cannot be bypassed.
How do you block datacenter traffic, Tor exit nodes, and bad bots on your storefront?
You can turn on automatic network and bot filters inside Settings > Mitigator, and combine them with targeted ASN rules in Blocking Rules > ISP. Follow along with screenshots in our bot and content protection guide.
Step 1: Save your Admin bypass link first
Before enabling network or ISP blocks—especially if you work remotely through a corporate proxy—go to Settings > General settings and copy your Admin access link (https://your-store.myshopify.com/?fg_bypass=...). Open that link once in your browser so our server verifies your token and your browser session skips every storefront rule while you test. Clicking Generate new link invalidates the old token immediately.
Step 2: Enable Datacenter, Tor, and Bot switches in Mitigator
In the LabX Fraud Filter navigation, open Settings and select the Mitigator tab:
- Toggle on
Block datacenter traffic: Stops visitors originating from known cloud compute, VPS, and server hosting ASNs without affecting shoppers on home broadband or consumer VPNs. - Toggle on
Block Tor traffic: Blocks connections matching the Tor Project’s published exit-node list, refreshed weekly on our server (note that a new exit node joining after the most recent weekly refresh is not listed until the next update). - Toggle on
Auto-block unknown bots: Blocks scripted HTTP clients and scrapers by user-agent signature (curl/,wget,python-requests,python-urllib,go-http-client,okhttp,headlesschrome,phantomjs,puppeteer,playwright, andselenium) ornavigator.webdriver. - Toggle on
Auto-block suspicious crawlers: Enable Unknown user agent (not a known browser) and Headless hints (webdriver, no plugins, no touch, no languages) to catch automated headless browsers.
Step 3: Add custom ASN or hosting provider rules in Blocking Rules > ISP
If you spot a niche hosting provider, regional server farm, or scraper network in your logs that you want to block, redirect, or explicitly allow, open Blocking Rules and click ISP:
- Use Common Datacenter & Cloud Samples: Click any quick-add button—
+ DigitalOcean (AS14061),+ Amazon Web Services (AWS) (AS16509),+ Hetzner Online (AS24940),+ Google Cloud (AS15169),+ Linode / Akamai (AS63949), or+ OVHcloud (AS16276)—to add the ASN immediately. - Enter any custom ASN or ISP name: Type comma-separated ASN codes (such as
AS14061, AS16509) or organization name substrings (such asHetznerorM247). - Block offending IP ranges or subnets: Open Blocking Rules > IP Address (detailed in our IP and location rules guide) to block exact IPv4/IPv6 addresses, prefixes (
IP Start With), CIDR blocks, or IP ranges manually or via CSV upload (up to 2,000 lines).
How does LabX block datacenter bots without hurting Googlebot or page speed?
As Google Search Central explains, legitimate crawlers like Googlebot run from data centers and crawl primarily from US IP addresses. LabX Fraud Filter protects your SEO rankings and Core Web Vitals through four safeguards:
- Good bots win at the top of the precedence order: Storefront evaluation follows a strict 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 before datacenter, Tor, and ISP rules, verified crawlers across Search Engines, Social Media, AI Crawlers, SEO Analytics, and Web Archives (including Googlebot, AdsBot-Google, Bingbot, Applebot, Facebookbot, GPTBot, ClaudeBot, AhrefsBot, and SemrushBot) always pass when Allow verified good bots is enabled. - Zero extra requests for non-geo rules: Your storefront ruleset travels in a Shopify metaobject rendered with the page HTML, so IP, user-agent, referrer, page, and product rules evaluate immediately with zero extra network calls.
- Single 30-minute cached GeoIP lookup: Location, ISP, Tor, and datacenter checks share one lookup per browsing session via the Shopify App Proxy, cached in the browser for 30 minutes.
- Fail-open reliability: If our server is unreachable or a visitor’s ASN cannot be determined, the guard fails open and lets the visitor through rather than locking real customers out.
How do you stop residential VPN fraud and API bots at checkout?
Because Shopify’s native Fraud Analysis only flags suspicious IP or proxy indicators after an order is placed—and post-order cancellation still leaves you paying non-refundable gateway fees, as covered in our Shopify Fraud Filter alternative comparison—you should pair storefront network rules with Checkout Protection (see our Checkout Protection setup guide):
| Threat Scenario | Why IP / Datacenter Blocking Alone Misses It | Server-Side Checkout Protection Rule to Add |
|---|---|---|
| Buyer in a restricted country using a consumer VPN | Consumer VPN masks the browsing IP behind a domestic residential exit node | Condition: Country or Zip — blocks the order server-side when the buyer enters a restricted shipping country or postal code (see our guide to blocking countries on Shopify) |
| API carding bot skipping storefront JavaScript | Script calls Cart/Checkout endpoints directly without loading the browser embed | Condition: Email (Contains) — block disposable email domains (@mailinator.com, @tempmail.com, @10minutemail.com, @guerrillamail.com, @yopmail.com, @trashmail.com, @sharklasers.com, @dispostable.com) |
| Reshipping fraud via residential proxy | Attacker browses from a residential IP but ships to a known freight forwarder | Condition: Address (Contains) and Phone — block freight-forwarder street substrings and repeated burner phone numbers (matched by digits regardless of formatting) |
| Repeat abuser rotating VPN IPs and emails | Attacker changes VPN exit nodes and email addresses on every attempt | Condition: Name, Address, or Customer tag — block repeated recipient names, street addresses, or tagged accounts across all Shopify plans |
Once your storefront and checkout rules are active, open Analytics and Visitor in LabX Fraud Filter (documented in our Analytics and Visitor log guide) to monitor your 7-, 30-, or 90-day block rate, block reasons, and the 50 most recent blocked or redirected visits.
Frequently asked questions
What is the difference between datacenter blocking and consumer VPN blocking on Shopify?
Datacenter blocking targets IP addresses belonging to cloud hosting providers and server farms (such as AWS, DigitalOcean, Google Cloud, and Hetzner), where automated scrapers and carding scripts run. Consumer privacy VPNs usually route traffic through residential or consumer networks and are not blocked by datacenter filtering.
Will blocking datacenter IPs and bots block Googlebot or hurt my SEO?
No, as long as "Allow verified good bots" remains enabled. LabX Fraud Filter evaluates a built-in allowlist of 25 search engine, social media, AI, and SEO crawlers at the top of the precedence order before checking datacenter, Tor, or ISP block rules.
Can a bot bypass storefront datacenter or IP blocking on Shopify?
Yes. Because Shopify serves storefront HTML from its CDN before app scripts run, storefront rules execute in the visitor browser via a theme app embed. A bot that disables JavaScript or calls the Cart and Checkout APIs directly can bypass browser checks, which is why you should pair storefront filtering with server-side Checkout Protection.
How do I stop a fraudster who uses a residential VPN at checkout?
Use server-side Checkout Protection powered by a Shopify Cart and Checkout Validation Function. Instead of relying on the visitor IP address, Checkout Protection runs on Shopify servers and blocks orders based on checkout form data—including email address, phone number, buyer name, street address, ZIP code, shipping country, or customer tag.
Sources
Part of our guide: Traffic & bot blocking →