Introduction: What You'll Get and Who This Guide Is For

A familiar situation: a website that opened without a problem yesterday now shows a 403 error. Or Google demands a CAPTCHA on every request. Or your ad account rejects your login, and your scraper returns empty pages instead of data. The first question that comes to mind is: is it my IP address or something else? You can't answer that by guessing. But you can check if your IP is blocked methodically, in a few clear steps, and get an accurate diagnosis instead of guesswork.

This guide is exactly about that. We won't dive into how blacklists work and why addresses end up on them—we have separate articles on that in the blog. Here it's all practice: how to find out in 15–40 minutes whether your address is restricted, where exactly, and at what level.

What You'll Get Out of It

  • A clear answer to whether your current IP is blocked or the problem lies elsewhere: your account, browser, or the site itself.
  • An understanding of the level at which the restriction applies: a specific website, an anti-bot system, a mail server, or your ISP's network.
  • A filled-in results table you can come back to in a week and compare.
  • A ready-made action plan for mobile proxies: when to change IP, when to wait, when to contact support.
  • For advanced users: scripts for bulk proxy checks and ideas for automated monitoring.

Who This Guide Is For

Primarily for those who work with mobile proxies every day: marketers running multiple ad accounts, media buyers with dozens of accounts, scraper developers, and business owners who collect competitor prices or promote product listings on marketplaces. But the instructions are written so that even someone who heard the word "proxy" last week can follow along. All terms are explained as we go.

What You Need to Know in Advance

Nothing special. You just need to be able to open a browser, copy text, and launch a program from your desktop. We'll open the command line together, step by step. If you have a mobile proxy, you'll need its details: address, port, username, password, and the IP change link from your dashboard.

How Much Time It Takes

  • Quick check (steps 1–3): 10–15 minutes.
  • Full check (steps 1–6): 30–40 minutes.
  • Advanced automation block: about an hour, but after that each check will take seconds.

Preliminary Preparation

The good news: you'll hardly need to install anything. All the tools are either already on your system or open right in your browser. But some things are worth preparing in advance so you don't get distracted along the way.

Required Tools and Access

  • Browser: Chrome, Firefox, Edge, or Safari up to date. You'll need incognito mode, which all of them have.
  • A second internet channel: a smartphone with mobile data (not Wi-Fi from the same network) or any other independent internet connection. This is the key element of the elimination method—without it, the result won't be complete.
  • Command line: on Windows, the Terminal or Command Prompt app; on macOS, the Terminal app; on Linux, any terminal emulator. Nothing to install.
  • The curl utility: built into Windows 10 and 11 since 2018; available by default on macOS and Linux.
  • Proxy credentials, if you're checking a mobile proxy address: host, port, username, password, connection type (HTTP or SOCKS5), and the IP change link.
  • A notepad or spreadsheet to record results. A plain text file or Google Sheet will do.
  • Optional: Python 3 for the advanced block. If it's not installed, it won't affect the basic and full checks.

System Requirements

Any computer or laptop made in the last ten years. Any modern operating system. A stable internet connection. You can even do the check from a tablet, though the command line will be awkward there.

What to Set Up in Advance

  1. Create a table with six columns: date and time, IP being checked, website or service, result without proxy, result with proxy, comment. Each row is one check.
  2. Open your proxy service dashboard and copy the connection details into a separate note. Verify that the IP change link works: click it and wait for a successful change confirmation.
  3. If you use an anti-detect browser, create a separate clean profile just for checks. No saved cookies or account logins should be in it.
  4. Write down what proxy settings are currently in your system and browser. This is your backup: after the checks, you'll restore everything as it was.

Tip: bookmark two or three IP detection services in your browser. You'll visit them dozens of times, and the extra seconds quickly add up to minutes.

About Backups

We won't break anything in your system, so a full backup isn't needed. The only thing you'll change during this guide is the proxy settings in your browser or system, and we've already recorded them in a note. If something goes wrong, just restore the previous values from that note.

Basic Concepts: What You Need to Understand Before You Start

Five minutes on terminology will save you half an hour of confusion in the following steps. We'll explain without unnecessary theory—only what you'll use in practice.

IP Address and Why You Have Two

An IP address is a numeric identifier for your connection on the network, for example 185.12.34.56. It's important to distinguish between the external (public) IP that websites see and the internal address of your device on your home network, like 192.168.1.10. Only the external one needs to be checked for blocking. When you enable a proxy, websites see the proxy server's address instead of your home one. So you'll need to check both: yours and the proxy's.

There are two formats: IPv4 (four numbers separated by dots) and IPv6 (a long notation with colons). Many ISPs in 2026 issue both simultaneously. A website may block one format and allow the other, so ideally you check both.

Blocking, Restriction, and CAPTCHA Are Different Things

  • Hard block: the site completely denies access. You see a 403 error, a blank page, or an access denied message.
  • Soft restriction (rate limit): the site slows you down or temporarily closes access after too many requests. Usually a 429 code and a "too many requests" message. It resolves on its own in minutes or hours.
  • CAPTCHA check: the site is suspicious but doesn't deny access. You solve the CAPTCHA and continue working. Frequent CAPTCHAs are a sign of declining address reputation, but not yet a block.
  • Account block: your profile is restricted, not the address. Another account from the same IP works fine. This is the most common confusion, and we'll learn to rule it out.

Levels at Which a Block Can Apply

  • Individual IP: exactly your address is blocked.
  • Subnet: a range of neighboring addresses is blocked, for example all 256 addresses like 185.12.34.x. You may have done nothing wrong but ended up in the same group.
  • Autonomous System (ASN): the entire network of an ISP or hosting provider is blocked. This happens with data centers that generate a lot of automated traffic.
  • Behavior: the address itself is clean, but your actions look like a bot, and the protection reacts to the pattern, not the IP.

HTTP Codes You'll See

  • 200: all good, the page is served.
  • 403: access forbidden. The most common sign of IP blocking, though the cause may be different.
  • 429: too many requests. A temporary restriction.
  • 451: access restricted for legal reasons.
  • 503: service unavailable. Sometimes an anti-bot check hides behind this code, sometimes the site is just overloaded.

The Special Case of Mobile IPs

Mobile carriers use NAT technology: hundreds or thousands of subscribers share one external IP simultaneously. For websites, this means blocking such an address is risky—along with one offender, thousands of regular users would be cut off. That's why mobile addresses are blocked less often and are more frequently restricted softly, through CAPTCHAs and limits. But the reputation of such an IP is shared: if a NAT neighbor behaved badly, it can affect you too. That's exactly why it's important to be able to quickly check a mobile proxy IP and change it if necessary.

Step 1: Determine Which IP to Check

Goal of this stage: get the exact external addresses you're working with and make sure the proxy actually substitutes its own IP and doesn't leak your own.

Sounds obvious, but about a third of incorrect blocking conclusions happen right here: someone checks one address while websites see another. Let's eliminate this mistake right away.

Instructions

  1. Make sure the proxy in your browser and system is disabled. In Chrome, open Settings, type "proxy" in the settings search, and go to the operating system's proxy server settings. On Windows, in the Proxy Server page, the "Use a proxy server" toggle should be off. On macOS, in System Settings, choose Network, your connection, Details, the Proxies tab, and uncheck everything.
  2. Open a new incognito window: Ctrl+Shift+N in Chrome and Edge, Ctrl+Shift+P in Firefox. On Mac, use Cmd instead of Ctrl.
  3. Type "what is my IP" in the address bar and open any of the first services in the results. 2ip, Whoer, Whatismyip, and similar will work. On the page you'll see a large highlighted address, and below it the city, ISP, and sometimes the connection type.
  4. Copy the address and paste it into the table in the "without proxy" row. If the service shows both IPv4 and IPv6, record both.
  5. Now enable the proxy. The easiest way is through a browser extension for proxy management or through an anti-detect browser profile. Enter the host, port, username, and password from your dashboard. Save and activate.
  6. Refresh the IP detection service page with F5. The address should change. The provider should switch to a mobile carrier, not remain your home ISP. Record the new address in the "with proxy" row.
  7. Check the same IP in the command line to make sure the proxy works outside the browser too. Open the terminal: on Windows, press the Win key, type "Terminal," and press Enter; on macOS, press Cmd+Space, type "Terminal," and press Enter. Enter the command, substituting your own details:

curl -x http://login:password@host:port https://api.ipify.org

The terminal will print the address in response. It should match what the browser showed through the proxy. If the proxy works over SOCKS5, replace http:// with socks5://.

Warning: if the address with and without the proxy is the same, the proxy didn't apply. Further checks will be meaningless because you'll be checking your home address and drawing conclusions about the proxy. Stop and sort out the connection before moving on.

Tip: check your IP with two different services. Sometimes one of them caches the result or shows an intermediate node's address. Matching across two services gives confidence.

Expected Result

Check: at least two addresses are recorded in the table: your own and the proxy's. They are different. The proxy's provider is a mobile carrier. The curl command through the proxy returned the same address as the browser.

Possible Issues

  • The address didn't change after enabling the proxy. Make sure the extension is active for this window, not another profile. Check that you didn't mistype the port. Verify that the proxy is paid for and hasn't expired.
  • The service shows only IPv6. That means your ISP prioritizes IPv6. For completeness, find a service that separately shows IPv4, or temporarily disable IPv6 in your network adapter settings during the check.
  • curl reports authentication error 407. The username or password is incorrect, or they contain special characters that need encoding. The @ symbol in a password, for example, is replaced with %40.
  • curl isn't found as a command. Older Windows builds may not have it. Update your system or use only browser-based checks for now.

Step 2: Test Access to a Specific Website from Two Channels

Goal of this stage: find out whether the access problem is related to your IP or the site is down for everyone. This is the elimination method—the most reliable way to check if your IP is blocked at the level of a specific resource.

The logic is simple. If the site doesn't open from your address but opens from another channel, the address is to blame. If it doesn't open from anywhere, the site is just down or unavailable in your region, and the IP is irrelevant.

Instructions

  1. Choose the site where the problem occurred. For example, let's take a hypothetical online store that started returning an error.
  2. Open an incognito window with the proxy active (or without a proxy if you're checking your home address). Incognito mode is essential: it cuts out saved cookies and sessions that could affect the site's response.
  3. Enter the site address and press Enter. Read carefully what appears on the screen. Record it verbatim in the table: error code, page title, message text. For example: 403 Forbidden, below it the line "Access denied" and a mention of Cloudflare.
  4. Take your smartphone, turn off Wi-Fi, and leave only mobile data. Open the same site in the mobile browser, also in private mode. Record the result.
  5. Compare the two records. If the site opened from your phone but not from the checked address, you almost certainly have an IP-based restriction. If it didn't open anywhere, the problem is on the site's end or regional.
  6. For extra confidence, search for a service like "Down for everyone or just me" and enter the domain. The service will check the site's availability from its own servers and show whether it responds at all.
  7. Get the exact HTTP code through the terminal. Enter the command, substituting the proxy and site address:

curl -I -x http://login:password@host:port -A "Mozilla/5.0" https://example.com

The -I flag requests only headers, and -A substitutes a browser string so the site doesn't reject the request just because it's from a utility. In the first line of the response, you'll see the code: HTTP/2 200, HTTP/2 403, and so on. Record it.

Warning: always log out of the site you're checking or use a clean profile. If you're logged in, the restriction may apply to the account, not the address. Comparing addresses honestly only works without authentication.

How to Read the Result

  • 403 or blank page from the checked IP, 200 from the phone. Address restriction confirmed. Move on to step 3 to understand the scale.
  • Same error from both channels. The site is down for everyone or for your region. Your IP is irrelevant; no need to check it further.
  • CAPTCHA from the checked IP, immediate content from the phone. The address is suspicious but not blocked. Reputation is reduced; we'll look at it in step 3.
  • 429 from the checked IP. Temporary limit. Wait 10–30 minutes and retry. If it repeats regularly, your load on the site is too high for one address.
  • The site opens but behaves strangely: doesn't return some data, shows empty search results. This could be a hidden block, where the site doesn't explicitly deny access but returns truncated content. Compare the page content from the two channels.

Tip: check not only the homepage but also the page where the problem occurred. Some sites let everyone onto the homepage but apply restrictions on search, catalog, or checkout pages.

Expected Result

Check: in the table, next to the site, there are two results: from the checked address and from the independent channel. You can say in one sentence whether the problem is related to the IP. For contentious sites, the exact HTTP code from curl is recorded.

Possible Issues

  • The phone connected to home Wi-Fi automatically. Check the network icon in the status bar: it should be LTE or 5G, not the Wi-Fi icon. Otherwise both channels will be the same address.
  • curl returns 403, but the browser opens the site. The anti-bot rejects curl by fingerprint. This isn't IP blocking but a client-type filter. Rely on the browser.
  • The site opened from browser cache. Press Ctrl+Shift+R for a full reload without cache.

Step 3: Check IP Reputation in Specialized Services

Goal of this stage: see the address through the eyes of anti-bot systems and mail servers. Understand whether it's flagged as suspicious and how widely that flag has spread.

Every major site checks reputation databases before letting you in. We'll look into the same databases. We won't dive into how they work—for practice, it's only important to read the verdict.

Instructions

  1. Start with a general check service. Search for "check if IP is blocked" or "check IP in blacklists," open one of the first results, for example the check section on 2ip or Whoer. Paste the address you're checking into the input field and click the Check button.
  2. Wait for it to finish. The service queries several dozen databases one by one; this takes from 10 seconds to a minute. The result looks like a list of databases with marks: clean, found, no response. Record how many databases out of the total the address was found in. For example: found in 2 out of 50.
  3. Open a risk scoring service, such as IPQualityScore or Scamalytics. Enter the address. Here you'll get a numeric Fraud Score or Risk Score from 0 to 100 and a set of flags: proxy, VPN, TOR, bot activity, recent abuse. Record the value and flags.
  4. Check the address in AbuseIPDB. This service collects reports from administrators about specific addresses. You'll see the Confidence of Abuse percentage and a list of recent reports with dates. Record the percentage and the date of the latest report.
  5. If you work with email campaigns or the problem is related to sending mail, open MXToolbox, the Blacklist Check tab, and check the address there. This tool focuses on email databases. The result looks like a table with green and red indicators next to each database.
  6. Look at the subnet. In IPQualityScore or Cloudflare Radar, enter the address and find the ASN and range information. If neighboring addresses have many reports, your address may be suffering by association.
  7. Record everything in one row of the table: number of databases, risk score, AbuseIPDB percentage, flags.

How to Interpret the Metrics

  • 0–2 databases out of 50, Fraud Score below 25, Abuse Confidence 0%. Clean address. If the site still won't let you in, the issue is behavior, browser fingerprint, or the site itself, not IP reputation.
  • 3–5 databases, Fraud Score 25–60. Borderline zone. Major sites will show CAPTCHAs, email may land in spam. For a mobile proxy, this is a reason to change the IP.
  • More than 5 databases, Fraud Score above 60, Abuse Confidence above 30%. Poor reputation address. Most protected resources will restrict it. Not worth working from it.
  • The proxy or mobile flag on a mobile proxy is normal and expected. Services honestly detect the connection type. A bad signal is flags like recent abuse, bot activity, and a high numeric score, not the mere fact of being identified as a proxy.

Tip: don't draw conclusions from one database. There are databases that add addresses automatically for any reason and are hardly used by real sites. Look at the big picture: how many databases, what risk score, are there recent reports.

Tip: record the date and time of the check. Mobile address reputation changes quickly: the same IP may be cleaner or dirtier a day later. Comparing records over time is more useful than any single check.

Expected Result

Check: for each checked address, the table has four numbers: number of databases where it was found, risk score, abuse percentage, and number of flags. You can categorize the address into one of three categories: clean, borderline, problematic.

Possible Issues

  • The reputation service itself won't open through the proxy. Some of them restrict access from proxy addresses. Open the service without a proxy and enter the proxy address manually; services allow checking any IP, not just the current one.
  • Results from different services contradict each other. This is normal; they have different sources. Rely on the majority and on the service closest to your task: MXToolbox for email, IPQualityScore for websites.
  • The service requires registration for a detailed report. The free version is enough for our task. The main score is visible without registration.

Step 4: Check Restrictions on Specific Platforms

Goal of this stage: find out how the services you actually work with treat the address: search engines, social networks, marketplaces, ad accounts. General reputation matters, but each platform has its own protection and its own signs of restriction.

The principle is the same for all: clean profile without logging in, the IP being checked, a repeatable action, recording the reaction. Below we'll cover what IP restrictions look like on popular platforms and how to distinguish them from account issues.

Search Engines

  1. In a clean profile with the checked IP, open Google and enter any three- to four-word query.
  2. If results appear immediately, the address is fine. If a page appears with text about unusual traffic from your network and a CAPTCHA, the address is under suspicion. If the CAPTCHA appears on every other query or blocks you entirely, reputation is seriously degraded.
  3. Repeat with Yandex. The sign of restriction is similar: a page asking you to confirm you're not a robot.
  4. Record: no CAPTCHA, one-time CAPTCHA, constant CAPTCHA, complete denial.

Social Networks

  1. Open the Instagram or Facebook homepage without logging in. If instead of the login form you immediately see an error page or a message that the request cannot be processed, the address is restricted at the network level.
  2. Try opening a public profile via a direct link. If it opens for an unauthenticated user from your phone but not from the checked IP, the restriction is confirmed.
  3. For VKontakte, open any public page. A sign of IP restriction is a CAPTCHA page before login or a message about suspicious activity from your address.
  4. For Telegram Web, check whether the login interface loads. A long load with no result when working fine from another channel indicates a network restriction.
  5. If you have a test account, log in. The difference matters: if the network let you in but a phone verification request appeared at login, the issue is the account or the newness of the account-plus-address combination, not an IP block as such.

Marketplaces and Online Stores

  1. Open Wildberries, Ozon, or another marketplace you need. Go to search and enter any product name.
  2. A sign of IP restriction: the homepage opens, but the search or catalog page returns an error, an empty result, or a message about temporary technical problems, while everything works from your phone.
  3. Open any product page via a direct link. Check that prices and stock display. Hidden restrictions on marketplaces often manifest exactly this way: the page exists but data doesn't come through.
  4. Pay attention to speed. If pages load in 15–20 seconds while they're instant from your phone, this may be deliberate throttling of suspicious addresses.

Ad Accounts and Business Tools

  1. Open the ad account login page. The form should load completely. If a network error appears instead, the address is restricted at the entrance.
  2. Don't log into a working account from an address you've just identified as borderline or problematic. This can add flags to the account. Change the IP first, then log in.
  3. Record the result for each platform separately: the same network may freely let you into a search engine and restrict access to an ad account.

Email

  1. If you have your own mail server or send emails via your own SMTP from the checked address, send a test email to a mailbox at a major provider.
  2. Open the delivery failure report if it arrives. A code 550 mentioning blocked, blacklisted, or poor reputation means the receiving server rejected it specifically because of the address. A code 421 usually means a temporary restriction; the email should be retried later.
  3. If the email arrived, check the Spam folder. Landing there with clean message content is also a signal about address reputation.

Warning: don't run dozens of checks in a row from one address on platforms. The very series of fast, identical requests looks like automation and can degrade the reputation of an address that was previously clean. Two or three checks per platform is enough.

Expected Result

Check: in the table, for each platform important to you, one of the statuses is recorded: works, CAPTCHA, partial restriction, complete denial. You see which services treat the address normally and which don't.

Possible Issues

  • The platform asks you to log in for any action. Only check what's available without login: the login page, public profiles, the catalog. This is enough to distinguish a network restriction from an account one.
  • The result changes from request to request. This is how probabilistic protection works: it doesn't deny always but increases the frequency of checks. Make five requests and record how many times the CAPTCHA appeared.

Step 5: Technical Diagnostics via Command Line

Goal of this stage: see exactly where along the path the connection breaks and get facts the browser won't show. This step isn't mandatory for a quick check, but it turns guesses into evidence and helps a lot when contacting support.

Don't be intimidated by the terminal. Each command below is one line you copy and paste. We'll explain what each response means.

How to Open the Terminal

  • Windows: press Win, type "Terminal" or "cmd," press Enter.
  • macOS: press Cmd+Space, type "Terminal," press Enter.
  • Linux: press Ctrl+Alt+T.

Instructions

  1. Check whether the site responds at the network level. Enter the command ping example.com, replacing example.com with the desired domain, and press Enter. On Windows, the command makes four requests and stops; on macOS and Linux, press Ctrl+C after a few seconds. You'll see either lines with response times in milliseconds or a timeout message.
  2. Read the result correctly. There's a response but the site doesn't open in the browser: the network reaches the server, and the restriction applies higher up, at the web server or anti-bot level. No response but the site opens: that's normal; many sites simply don't respond to ping. No response and the site doesn't open: move to the next step.
  3. Trace the route. On Windows, enter tracert example.com; on macOS and Linux, traceroute example.com. The command shows the chain of nodes from your computer to the site, up to 30 lines. Each line is one intermediate node with a response time. Wait—execution can take up to two minutes.
  4. Find where the path breaks. If asterisks instead of times appear only in the last one or two lines, while all previous nodes respond, packets reach the site's network and are dropped there. This is a typical picture of a filter on the resource's side. If asterisks start early, at the third to fifth node, the problem is in your ISP's network and has nothing to do with your IP being blocked.
  5. Check DNS. Enter nslookup example.com. The response should contain one or more IP addresses of the site. If instead there's an error like "can't find" or an address like 127.0.0.1, the domain isn't resolving through your DNS server. This isn't your IP being blocked but a DNS issue. Compare with the response on your phone via mobile network.
  6. Get the full web server response. Enter the command with or without the proxy:

curl -v -A "Mozilla/5.0" -x http://login:password@host:port https://example.com -o /dev/null

On Windows, write NUL instead of /dev/null. The -v flag enables verbose output. You'll see the connection being established, the headers sent, and those received. Pay attention to lines starting with the less-than sign: those are the server's response.

  1. Look for clues in the headers. The line server: cloudflare together with code 403 and the cf-ray header means Cloudflare's protection stopped you. The retry-after header with code 429 tells you how many seconds to wait before retrying. Headers mentioning akamai, incapsula, ddos-guard point to other protective systems. A 403 without such headers and with a short response body most often means a rule on the web server itself.
  2. Record in the table: ping result, the node number where the route broke, the code and key headers from curl.

Tip: save the full curl output to a file by adding a greater-than sign and a filename at the end of the command, for example > report.txt. You can attach such a file to a support request with your proxy service or the site, and they'll figure it out much faster.

Expected Result

Check: you can name the level at which the restriction applies: ISP network, site network, anti-bot system, or the web server itself. You have the exact response code and the name of the protective system, if any.

Possible Issues

  • tracert shows asterisks everywhere, starting from the first node. Your router or firewall blocks service packets. This isn't related to the site you're checking. Skip this item and rely on curl.
  • curl hangs with no response. Add the --max-time 20 flag so the command finishes after 20 seconds. Hanging with no response while working fine from another channel usually means packets are being silently dropped—also a form of blocking.
  • SSL error when connecting through the proxy. Check your system time: a discrepancy of more than a few minutes breaks certificate validation. If the time is correct, the problem may be with the proxy itself; try another port or protocol.

Step 6: Check Your Mobile Proxy and Change IP If Needed

Goal of this stage: apply all previous steps to your working mobile proxy, decide whether to change the address, and make sure the new address is clean. This step is what turns a one-time check into a working process.

A mobile proxy is designed so that its address isn't permanent. The carrier periodically reassigns it on its own, and you can trigger a change via the link from your dashboard or by timer. This is a standard feature: it's needed to distribute load and avoid working from one address for too long. But each change is a lottery: the new address may be cleaner or dirtier than the previous one. So after a change, a check is mandatory.

Instructions

  1. Connect the proxy in a separate clean profile, as you did in step 1. Verify via an IP detection service that the address was substituted and the provider is a mobile carrier.
  2. Go through steps 2, 3, and 4 for this address. In practice, this takes about 10 minutes: two or three target sites, one reputation service, one or two key platforms.
  3. Evaluate the result in three categories. Clean: you can work; record the address and time. Borderline: CAPTCHAs, medium risk score. Problematic: denials, high score.
  4. If the address is borderline or problematic, change it. Open your proxy service dashboard, find the IP change link for this proxy, and click it in the browser. You'll see a response like "IP successfully changed" or the new address. The change takes from a few seconds to half a minute.
  5. Refresh the IP detection service page. The address should change. If it stayed the same, wait 30 seconds and refresh again: the carrier needs time.
  6. Repeat the quick check for the new address: reputation and one target site. Record every address in the table, even failed ones. In a week, you'll see which ranges of this carrier are cleaner.
  7. If three changes in a row give problematic addresses on the same platform, the issue is likely not specific IPs but the platform's attitude toward the carrier's entire range in that region. Contact proxy service support with your table and ask for a port from another carrier or region.
  8. Set a reasonable rotation interval. Your dashboard usually has automatic time-based rotation. For working with protected platforms, changing the address too often within one session is harmful: the service sees the account jumping between addresses. Too rare is also bad: load accumulates on one IP. Start with an interval where the address lives as long as your typical work session, and adjust based on check results.

Warning: after changing the IP, don't continue working in the same browser profile with the same cookies if you're testing the platform's reaction to the new address. The site will link the new address to the old session, and you won't get a clean result. For checks, use a new profile or clear site data.

Tip: check the proxy at the same time of day when you plan to work. In the evening, the carrier's network load is higher, more addresses are in use in NAT, and the reputation of the same range may differ from the morning.

Expected Result

Check: you have a working proxy address that passed checks on target platforms and has a low risk score. It's recorded in the table with date and time. You know how to change it in half a minute and how to make sure the new address isn't worse.

Possible Issues

  • The IP change link responds that changes are allowed no more than once every N seconds. This is protection against too-frequent requests. Wait the specified time.
  • After changing the IP, the platform still shows CAPTCHAs. Check that you're in a clean profile. If so, look at the new address's reputation: maybe you just got unlucky; change again.
  • The proxy dropped after the change. Wait a minute and reconnect. If that doesn't help, check the port status in your dashboard and contact support if needed.

Verifying the Result: Checklist and Interpretation

You've gone through all the steps. Let's make sure nothing was missed and turn the table into a clear conclusion.

Checklist of Completed Actions

  • External addresses recorded: your own and the proxy's. They're different; the proxy is applied correctly.
  • Target sites checked from two independent channels in incognito mode.
  • For each address, reputation metrics recorded: databases, risk score, reports, flags.
  • Key platforms checked without logging in; results recorded.
  • For contentious cases, there's curl output with code and headers.
  • Mobile proxy checked; if necessary, the address was changed and rechecked.
  • All results in the table with date and time.

Four Final Scenarios

  1. The site doesn't open only from your address, reputation is bad, curl returns 403 with anti-bot signs. Your IP is restricted on this resource. For a mobile proxy, the solution is: change the address and recheck. For a home address: wait a day, make sure no automated traffic is coming from your network, and contact your ISP if needed.
  2. The site doesn't open only from your address, but reputation is clean and curl returns 403 without anti-bot signs. Most likely a targeted rule on the site itself: the range or region is restricted. Check addresses from the same carrier in another region.
  3. The site opens but with CAPTCHAs and slowdowns, reputation is borderline. The address is under observation but not blocked. Reduce request intensity or change the IP before starting important work.
  4. The site doesn't open from any channel. The problem is on the site's end or regional. Your IP is clean; further address-related actions are pointless—just wait.

Success Indicators

You've succeeded if you can answer three questions in one minute: is the address blocked, where exactly, and what to do about it. If you don't have an answer to at least one, go back to the relevant step: step 2 answers the first question, steps 3–5 the second, step 6 the third.

Common Mistakes and Their Solutions

Below are situations where even careful users reach wrong conclusions. Check yourself against this list if the result seems strange.

Mistake 1: Checking the Wrong Address

Problem: you checked the IP, it's clean, but the site still won't let you in. Cause: the proxy didn't apply to the window or app making the request, and the site sees a different address. Solution: open the IP detection service in the same window and profile where the problem occurs. Check exactly the address shown there.

Mistake 2: Account Block Mistaken for IP Block

Problem: you can't log into the account from the address, so you conclude the IP is blocked. Cause: the profile is restricted, not the network. Solution: log out and check access to the platform's public pages from the same address. If they open, the IP is fine.

Mistake 3: IPv6 Ignored

Problem: IPv4 is clean, but the site returns an error. Cause: the browser connects via IPv6, and that address is restricted. Solution: check IPv6 separately or temporarily disable it in your network adapter settings and repeat the test.

Mistake 4: Ping Treated as a Block Indicator

Problem: ping doesn't go through, so you conclude there's a block. Cause: most major sites don't respond to ping at all. Solution: use ping only as a secondary signal. The decisive indicator is the curl or browser response.

Mistake 5: Panicking Over One Database

Problem: the address was found in one list out of fifty, so you decide to urgently change everything. Cause: some databases add addresses automatically and are hardly used by anyone. Solution: look at the combination: number of databases, risk score, recent reports, and the actual reaction of target platforms.

Mistake 6: Result Distorted by Cache

Problem: after changing the IP or settings, nothing changed. Cause: the browser shows a saved copy of the page, and the system caches DNS. Solution: reload the page with Ctrl+Shift+R; for DNS, run the Windows command ipconfig /flushdns in the terminal, or on macOS sudo dscacheutil -flushcache.

Mistake 7: Temporary Limit Mistaken for Permanent Block

Problem: code 429, so you conclude the address is banned forever. Cause: this is a request rate limit; it lifts automatically. Solution: check the retry-after header, wait the specified time, reduce request intensity.

Mistake 8: The Check Itself Degrades Reputation

Problem: after a series of checks, an address that was clean starts getting CAPTCHAs. Cause: dozens of fast, identical requests look like automation. Solution: two or three checks per platform, pauses between them, no loops of a hundred requests from your working address.

Mistake 9: curl Without a Browser Header

Problem: curl returns 403, the browser opens the site. Cause: the anti-bot rejects the request due to missing real-browser headers, not because of the IP. Solution: always add the -A flag with a browser string and compare the result with the browser.

Advanced Extras

If you have dozens of proxies rather than one, manual checking of each gets tiring. This block is for developers and those ready to spend an hour on automation to save it every day afterward.

Bulk Checking a Proxy List with One Command

Create a proxies.txt file where each line is a proxy in the format http://login:password@host:port. Then, in the macOS or Linux terminal, run:

for p in $(cat proxies.txt); do echo -n "$p "; curl -s -o /dev/null -w "%{http_code}" -x "$p" -A "Mozilla/5.0" --max-time 15 https://www.google.com; echo; done

The command will go through each proxy and print the target site's HTTP response code next to it. Lines with code 200 are working addresses; 403 and 429 need attention; 000 means the proxy didn't respond within 15 seconds. Replace the site address with the one you work with.

Python Script with Multiple Platform Checks

If Python 3 and the requests library are installed, create a check.py file with the following lines; each list line is one line of the file—maintain four-space indentation inside loops and blocks:

  1. import requests
  2. proxy = 'http://login:password@host:port'
  3. proxies = {'http': proxy, 'https': proxy}
  4. headers = {'User-Agent': 'Mozilla/5.0'}
  5. targets = ['https://www.google.com', 'https://www.instagram.com', 'https://www.wildberries.ru']
  6. for url in targets:
  7. try:
  8. r = requests.get(url, proxies=proxies, headers=headers, timeout=15)
  9. print(url, r.status_code, r.headers.get('server', ''))
  10. except Exception as e:
  11. print(url, 'error', e)

Run it with the command python check.py. The script will output the response code and web server name for each platform. It's easy to extend: add saving to CSV with a timestamp, and you'll have a reputation history for each address.

Checking Reputation via API

IPQualityScore, AbuseIPDB, and several other services have APIs with free request limits. Register, get a key, and add an API request to your script after detecting the proxy's current IP. Then one command will output both the platforms' reactions and the risk score. Read the specific service's documentation: response formats differ, but the risk score usually lies in a field like fraud_score or abuseConfidenceScore.

Determining ASN and Subnet

The command whois 185.12.34.56 in the terminal will show the range's owner, its size, and the autonomous system number. This helps you understand whether only your address or the whole carrier's range is restricted. If several problematic addresses share the same ASN and the first three numbers, the restriction almost certainly applies to the subnet, and changing IP within the same range won't help.

Monitoring with Notifications

Schedule the check script: cron on Linux and macOS or Task Scheduler on Windows. Run it every 30–60 minutes with your working proxies and send a messenger notification if the target platform's response code changes from 200 to anything else. That way you'll learn about a problem before your ad campaign or scraper notices it.

Tip: keep check history for at least a month. It answers questions otherwise solved by guessing: what time of day addresses are cleaner, which carriers and regions are more stable for your platform, how quickly reputation recovers after a change.

What Else to Consider with Automated Checks

  • Don't check from one address more often than a real person would. An interval of a few seconds between requests to different sites is enough.
  • Separate addresses for checks and addresses for work, if your plan allows. That way checks never affect your working reputation.
  • Log not only the code but also the response time. Rising delays on one address often precede the appearance of CAPTCHAs.

FAQ: Common Questions About Checking IP

How do I know if the IP is blocked and not my account?

Log out and open the service's public pages from the same address in incognito mode. If they open, the address is fine and the account is what's restricted. If they don't open but do open from another channel, the restriction is network-based.

Is one reputation check service enough?

For a rough estimate, yes; for deciding whether to change the address, no. Different services rely on different sources. Compare at least two and add the target platform's actual reaction—it matters more than any score.

The mobile IP is detected as a proxy. Is that bad?

No, it's expected. Services honestly detect the connection type. Pay attention to the risk score and recent abuse flags, not the mere fact of being detected as mobile or proxy.

How often should I check a mobile proxy IP?

Before each important session and after each address change. If work is continuous, an automatic check every 30–60 minutes using the advanced block's scheme is enough.

How long should I wait if the address hit a temporary restriction?

Rely on the retry-after header with code 429. If it's absent, the typical period is from 15 minutes to several hours. For a mobile proxy, changing the address is faster and more reliable than waiting.

Can I check if my IP is blocked from my phone?

The browser steps (IP detection, reputation services, platform checks) are fully available from a phone. The command line is more convenient on a computer, though terminal apps exist for mobile devices too.

Why does the site open in the browser but curl gets 403?

Anti-bot systems check not only the address but also client signals: headers, their order, support for modern protocols. A utility without a browser header looks suspicious on its own. Add the -A flag and compare; if the difference persists, rely on the browser.

What if after several IP changes all addresses are problematic?

This is a sign that the platform restricts the carrier's entire range in the region. Compile a table with addresses and results and contact proxy service support asking for a port from another carrier or region.

Can the check itself harm the address reputation?

It can if you make dozens of fast requests in a row. Two or three checks per platform with pauses are safe. For regular monitoring, use a moderate interval and, if possible, separate addresses.

Do I need to roll anything back after the check?

Only the proxy settings if you changed them in the system or browser. Restore the values from the note you made during preparation and close the profiles created for checks.

Conclusion: What's Done and Where to Go Next

Let's sum up. You've identified the exact addresses you work with and made sure the proxy substitutes its own IP. You checked target sites from two channels and learned to distinguish an address problem from a site problem. You looked at the address's reputation through the eyes of anti-bot systems and mail servers. You checked specific platforms' reactions without account influence. You got technical evidence via the command line. And finally, you applied all of this to your mobile proxy: evaluated the address, changed it if needed, and rechecked the new one.

The main result isn't even the specific verdict on today's address. The main thing is that you now have a repeatable process. Next time a scraper starts returning empty pages or an ad account asks for confirmation, you won't be guessing—you'll check if your IP is blocked in 10–15 minutes and know exactly what's happening.

What to Do Next

  • Save the table and add to it with each check. In a month, it will become your personal map: which carriers, regions, and times of day work best for your platforms.
  • Add a quick check to your workflow: before launching a campaign, before bulk scraping, after each address change.
  • If you have several proxies, set up automatic checking from the advanced block. An hour of setup will pay off in the first week.

Where to Develop

The next logical step is managing address reputation over the long term: how to structure request intensity so clean addresses stay clean, how to separate addresses for different tasks, and how to coordinate IP rotation with account lifecycles. Read about that, as well as how blacklists work and why addresses end up on them, in other blog articles. And the basic skill underlying all of it, you already have: you know how to quickly and accurately check if your IP is blocked.