How to Test Your Proxies Before a Drop: A Step-by-Step Guide

Why Testing Proxies Matters

You've got your bot configured, tasks ready, profiles loaded, and proxies imported. The drop is in 30 minutes. Everything looks good — but have you actually tested your proxies?

Skipping proxy testing is one of the most common mistakes in the botting community. It's also one of the most costly. Here's what happens when you run untested proxies on a drop:

• Dead proxies waste task slots that could be running on working IPs
• Banned proxies trigger immediate blocks, and repeated attempts can flag your payment profiles
• Slow proxies miss the checkout window entirely on speed-sensitive sites like Shopify and Supreme
• Misconfigured proxies fail silently, and you won't know until the drop is over

Testing takes 5 minutes. Not testing can cost you an entire release.

When to Test Your Proxies

Timing matters. Test too early and the results might not reflect conditions at drop time. Test too aggressively and you risk getting flagged before the release.

The Ideal Timeline

When	What to Do
24 hours before	Import proxies into your bot. Do a quick format check (no errors on import).
2-4 hours before	Run a basic connectivity test against a neutral URL to catch dead proxies.
30-60 minutes before	Run your bot's proxy tester against the actual target store URL.
5 minutes before	Glance at test results. Remove any that failed. Don't retest.

What NOT to Do

• Don't test every hour all day. Each test generates requests. Excessive testing from the same IPs can flag them before the drop even starts.
• Don't test against the target site at low-traffic times. If the site sees 50 rapid connections at 3 AM from IPs that never visited before, that's suspicious.
• Don't test and re-test failed proxies repeatedly. If a proxy fails twice, remove it. Retrying just adds more flagged requests from a bad IP.

Step-by-Step Testing Process

Step 1: Import and Format Check

First, make sure all your proxies imported correctly into your bot without errors.

Common format issues:

• Extra spaces or blank lines in your proxy list
• Wrong delimiter (using commas instead of colons)
• Missing authentication credentials
• Mixing formats (some ip:port:user:pass, others user:pass@ip:port)

Your proxy list should look clean, one proxy per line:

192.168.1.1:8080:username:password
192.168.1.2:8080:username:password
192.168.1.3:8080:username:password

If your bot shows import errors, fix the format before proceeding.

Step 2: Basic Connectivity Test

Most bots have a built-in proxy tester. For the initial check, test against a neutral, fast-responding URL. Some bots default to testing against https://www.google.com or their own API endpoint.

What you're checking:

• Does the proxy connect? If it times out, it's dead — remove it.
• What's the response time? Anything under 200ms for datacenter proxies is good. Under 500ms for residential.
• Is the response valid? Some "connecting" proxies return error pages or captchas. Your bot should flag these.

Step 3: Test Against the Target Site

This is the most important test. A proxy that works on Google might be banned on your target Shopify store. Run your bot's proxy tester with the actual store URL.

For example, if you're targeting https://kith.com:

• Set the test URL to https://kith.com
• Run the test
• Look for 200 (OK) responses

Status codes to watch for:

Status Code	Meaning	Action
200	Success	Keep the proxy
403	Forbidden / Banned	Remove the proxy
429	Rate limited	Proxy might be overused — consider removing
407	Auth required	Check your username/password
503	Service unavailable	Might be temporary — retest once
Timeout	No response	Remove the proxy

Step 4: Review and Clean Up

After testing, clean up your proxy list:

1. Remove all failed proxies (403s, timeouts, auth errors)
2. Remove slow proxies (>300ms for datacenter, >800ms for residential)
3. Count your remaining working proxies — do you still have enough for your tasks?
4. If you're short on proxies, either reduce task count or get more proxies

A good rule of thumb: if more than 20% of your proxies fail testing, consider reaching out to your provider. Quality proxy providers should have very low failure rates on supported sites.

Understanding Test Results

Speed (Latency)

Proxy speed is measured in milliseconds (ms) — the time it takes for a request to go from your server through the proxy to the target site and back.

• 0-50ms: Excellent (fast datacenter proxies)
• 50-150ms: Good (standard datacenter)
• 150-300ms: Acceptable (datacenter with distance or residential)
• 300-500ms: Slow (will hurt checkout speed on Shopify)
• 500ms+: Too slow for competitive drops

For Shopify and Supreme, aim for under 150ms. For SNKRS draws (which are luck-based, not speed-based), up to 500ms is acceptable.

Success Rate

Your success rate is the percentage of proxies that returned a valid 200 response from the target site.

• 95-100%: Excellent — your proxy batch is clean
• 80-95%: Good — remove the failures and you're set
• 60-80%: Concerning — may indicate the subnet is partially burned
• Below 60%: Bad batch — contact your provider or get new proxies

Geographic Distribution

If your bot shows proxy locations, check that they match your needs:

• US East proxies for US Shopify stores
• EU proxies for European stores
• Residential IPs should be from the country the site serves

Testing Without a Bot

If you want to test proxies outside of your bot, you can use command-line tools:

curl -x http://username:password@proxy_ip:port https://target-site.com -o /dev/null -s -w "HTTP Code: %{http_code}\nTime: %{time_total}s\n"

This shows you the HTTP status code and total request time. It's useful for quick spot-checks, but for testing a full list, your bot's built-in tester is more efficient.

Common Testing Mistakes

Over-Testing

Every test request is a real HTTP request to the target site. Running 100 test requests from 100 IPs in 30 seconds looks like a bot attack. The site may preemptively block those IPs.

Fix: Test once, 30-60 minutes before the drop. One round of testing is enough.

Testing the Wrong URL

Testing against google.com only proves your proxy connects to the internet. It doesn't tell you if the proxy is banned on your target site.

Fix: Always test against the actual store URL you'll be botting.

Ignoring Slow Proxies

A proxy that "works" but takes 400ms to respond will lose the checkout race to someone with 50ms proxies. Just because it connects doesn't mean it's good enough.

Fix: Set a speed threshold and remove anything above it. For Shopify, 200ms is a reasonable cutoff for datacenter proxies.

Testing on Your Local Network

If your bot runs on a cloud server (which it should for competitive drops), test from the server, not from your home computer. Network conditions between your home and the proxy are different from your server to the proxy.

Fix: Run all proxy tests from the same server that will run your bot during the drop.

Panic-Testing 5 Minutes Before

If your proxies were good an hour ago, they're still good. Retesting at the last minute generates unnecessary requests and adds stress without providing useful information.

Fix: Trust your earlier test results. Focus on making sure your tasks and profiles are ready instead.

Pre-Drop Proxy Checklist

Use this checklist before every major release:

• Proxies imported without format errors
• Connectivity test completed (neutral URL)
• Site-specific test completed (target store URL)
• Failed and slow proxies removed
• Proxy count matches or exceeds task count
• Proxy location matches target site region
• Proxy list assigned to correct task group in bot
• Separate proxy lists for different sites (not shared)
• Backup proxies available if needed

The Bottom Line

Testing proxies is a small time investment that dramatically improves your success rate. The process is straightforward: import, format check, connectivity test, site-specific test, clean up. Do it once before every drop, and do it from the same server your bot runs on.

The difference between a successful drop and a wasted one is often preparation, not luck. Tested proxies are prepared proxies.

Ready to get proxies you can rely on? Check out Zenu's plans — we keep our IP pools fresh and our speeds fast so your tests come back green.

---

Related guides:

• Residential vs Datacenter Proxies: Complete Comparison Guide
• Best Proxies for Shopify: Setup Guide