IP purity check
Test your IP as soon as the page opens: network type, native or broadcast, the SpamCop blacklist, time zone, language and WebRTC, plus how to read each result.
How to read the listing, what to fix if the address is yours, and who to ask if it is not.
"Blacklist" is a catch-all word. In practice you will meet lists that mail systems query before accepting a message, such as the SpamCop Blocking List (SCBL). SpamCop describes the SCBL as a list of IP addresses that have transmitted reported email to SpamCop users; it is time-based, which means listings clear automatically when reports stop.
The list name in a lookup matters more than the yes or no, because it tells you what kind of problem you have. A listing about mail behaviour calls for a mail fix. A listing on an address you only browse from is a different situation, covered in Section 4.
A bounce message (a non-delivery report, NDR) usually names the sending address. Microsoft's documentation shows NDRs such as "550 5.7.606-649 Access denied, banned sending IP" that carry the IP and tell you where to ask for removal.
not a third-party mirror. Spamhaus publishes an IP and domain reputation checker that it describes as a free tool, and SpamCop offers a lookup form on its blocking-list page.
Reverse the octets of the IP and query them under the blocklist domain, for example 4.3.2.1.bl.spamcop.net for 1.2.3.4, using nslookup, host or dig. An answer such as 127.0.0.2 means the IP is listed; a non-existent-host answer means it is not.
The Spamhaus troubleshooting article lists what its checker tests: whether the IP has a reverse DNS (PTR) record, whether there is a valid HELO domain that matches the reverse DNS record, and whether the values agree with each other.
Spamhaus's FAQ says a DNS resolver issue can hide a listing, and that if a recent removal has not taken effect yet, some networks update slowly and you should wait one to two hours.
If you run the mail server, you are the one who can fix the cause and ask for a review. Work through the steps in order.
Spamhaus's troubleshooting article treats removal as the last step, after the issues the checker finds are fixed.
The article's resolution steps require the HELO domain to resolve to the sending IP, the reverse DNS to resolve to a fully qualified domain name, and the reverse record to match the HELO domain and resolve back to the sending IP. If any check shows a red cross, the article says any removal request is likely to be unsuccessful.
Spamhaus's residential-network FAQ describes a device behind the address (for example a smartphone or streaming stick) making unauthorised SMTP connections on port 25. Its advice: restrict port 25 so only the mail server uses it, make all user devices send mail with SMTP authentication on ports 587 or 465, and remember that limiting port 25 stops the spam but the affected device still needs to be cleaned or removed.
contact whoever does, such as your administrator, ISP or email provider. Spamhaus says removal requests must come from the registered owner of the IP or domain, and others should contact their service provider.
Spamhaus says it cannot handle removal requests made through other channels such as email. It also says requests should not be made through a VPN or from a free or disposable email address. If automatic removal is not permitted, the checker raises a ticket for review.
Following the article gives the IP the best chance of removal, but approval is decided by the operator.
Because the SCBL is time-based, an address drops off automatically once reports stop; there is no request to file with an owner.
Microsoft provides the Office 365 Anti-Spam IP Delist Portal for errors in the 5.7.606–649 range. You enter the address that received the NDR and the IP from the error, one of each per visit, confirm through the email you receive and select Delist IP. Microsoft notes that this can take up to 24 hours or longer. For error 5.7.511 the portal cannot be used: you send the NDR code and IP to the delist address given in the error, and Microsoft says it will respond within 48 hours.
Here the situation differs in one decisive way: you probably do not control the address, and the listing is about mail rather than browsing.
A mail blocklist is consulted by receiving mail systems. A browsing session does not send mail, so a listing on your exit address does not by itself describe your browsing.
Whether it is a residential, ISP or datacenter address decides who can act. The guides on checking IP type and static and dynamic IPs explain the difference.
If the reason is mail behaviour, such as unauthorised SMTP connections on port 25 from a device behind the address, the address belongs to an access network and the fix sits with that network's operator.
Spamhaus advises, for a dynamic address with no mail server, asking the ISP to block or disable port 25 for the connection, and sending mail through the ISP's mail server or a trusted third-party service with authentication on ports 587 or 465. If the address sits behind carrier-grade NAT, Spamhaus says the traffic may come from another customer sharing the same address pool, and only your IP provider can investigate that.
since Spamhaus accepts removal requests only from the registered owner.
treat the listing as a data point. The IP purity check guide covers looking at an exit address's reputation before you rely on it, and checking a proxy IP's location confirms where a session appears from.
check the connection itself before blaming the address, because connection failures often come from credentials, protocol or endpoint settings.
For work that needs the same exit each time, a static ISP IP stays fixed for the lease term. Proxy302 rents these per IP, from static ISP proxies, and you pick the protocol when you generate the proxy: HTTP on port 2222 or SOCKS5 on port 3333 at proxy.proxy302.com.
An IP change only alters the network address a service sees; decisions about accounts stay with the platform. These steps still help:
Write down the list name, the date, the stated reason and any evidence for a later conversation with your ISP or provider.
Fix anything on your side that really sends mail from the address, following the port 25 and authenticated-submission advice above.
Ask the party that owns the address to act, if that is not you.
Look the address up again later, since a recent removal can take an hour or two to show.
For the task itself, test from an address type that fits the job while the listing question is handled.
Proxy302 rents static ISP IPs that stay fixed for the lease term, so you can check an address once and keep using the same one.
Look up the IP you receive the same way, then use the gateway proxy.proxy302.com with the protocol you generated: HTTP on port 2222 or SOCKS5 on port 3333.
Open the product page that fits (static ISP, rotating residential or the ISP for AI subscriptions) and pick the region, traffic or lease term, and quantity. For per-IP products also choose HTTP or SOCKS5.
After the proxy is generated, open My assets and copy HOST, PORT, USERNAME and PASSWORD.
Open https://ipinfo.io/json through the proxy and check that the country and org fields (ASN and organization) are what you expected.
Then compare network type and native or broadcast on the IP purity check page. Two tools disagreeing is normal; go by your actual use.
Rotating residential starts at US$1.50 per GB on the Budget line and US$5 per GB on the Premium line; larger packages are cheaper per GB, and purchased traffic has no expiry. A static ISP IP is US$0.50 for one day or US$7.99 for 30 days, the same in every country, fixed for the lease. A datacenter IP is US$0.25 for one day or US$3.99 for 30 days. Stock changes daily, so go by the order page. The smallest purchase is 1 GB of traffic or one IP for one day. Changing IP does not lift a restriction or raise a limit; what happens to an account is up to the platform.
| Item | Price | Protocols | Locations |
|---|---|---|---|
| Rotating residential | From US$1.50 per GB (Budget line); US$5 per GB (Premium line); lower per GB in larger packages | HTTP, SOCKS5 | 195+ countries and regions; state and major city on lines that support it (small towns and some connections exit at country level; no city level in Russia and Singapore) |
| Static ISP, per IP | US$0.50 for 1 day, US$7.99 for 30 days, the same in every country | HTTP or SOCKS5, chosen per IP | 30 countries on the order form; stock changes daily |
| ISP for AI subscriptions | Per 30 days: Claude 15 PTC, GPT / Grok 10 PTC, Gemini 8 PTC | HTTP or SOCKS5 | Claude: US, UK, DE, JP. GPT / Grok: US, UK, FR, JP, KR. Gemini: US, UK, FR, JP |
| Datacenter, per IP | US$0.25 for 1 day, US$3.99 for 30 days | HTTP or SOCKS5, chosen per IP | 8 countries |
Prices are in PTC, paid from the wallet; 1 PTC = US$1. There is no free trial: the smallest purchase is 1 GB of rotating residential traffic or one IP for one day. Checked on 9 November 2026.
Spamhaus describes its checker as a free tool, and SpamCop offers a public lookup form on its blocking-list page.
SpamCop describes its list as time-based, with quick automatic delisting when reports stop, so the route is to fix what generated the reports and let the listing clear.
Spamhaus's FAQ on residential networks attributes many such listings to a device behind the address making unauthorised SMTP connections on port 25, not to a mail server you run.
The operator decides. Spamhaus says a recent removal may take one to two hours to show on slower networks, and Microsoft says delisting from its blocked senders list can take up to 24 hours or longer.
Contact the ISP. Spamhaus's advice for a dynamic home address is to ask the ISP to block or disable port 25 and to send mail through the ISP's server or a trusted service using authentication on ports 587 or 465.
Official documentation · Confirmed on:
Read on 9 November 2026: the checker is a free tool; it tests reverse DNS (PTR), a valid HELO domain matching it and forward-confirmed values; any red cross makes a removal request likely to fail; unresolved cases become a ticket.
Official documentation · Confirmed on:
Read on 9 November 2026: removal requests go through the checker only, from the registered owner, not via VPN or free or disposable email; slower networks may need 1 to 2 hours; a DNS resolver issue can hide a listing.
Official documentation · Confirmed on:
Read on 9 November 2026: a device behind the address can make unauthorised SMTP connections on port 25; restrict port 25, use SMTP authentication on ports 587 or 465, ask the ISP to block port 25 on a dynamic connection; behind CGNAT only the IP provider can investigate.
Official documentation · Confirmed on:
Read on 9 November 2026: reverse the octets and query them under bl.spamcop.net with nslookup, host or dig; an answer such as 127.0.0.2 means listed, a non-existent host answer means not listed.
Official documentation · Confirmed on:
Read on 9 November 2026: the SCBL lists IPs that transmitted reported email to SpamCop users and is time-based, with quick automatic delisting when reports stop; the page has a lookup form.
Official documentation · Confirmed on:
Read on 9 November 2026: the Office 365 Anti-Spam IP Delist Portal handles 5.7.606-649 errors with one email address and one IP per visit and can take 24 hours or longer; for 5.7.511 you send the NDR code and IP to the delist address and Microsoft responds within 48 hours.
Product observation · Confirmed on:
Product facts file of the site, checked 9 November 2026 against the console, the backend and the price table: products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, countries, quantity limits, no free trial.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.