Per month. A 3-month term is $10/mo less.
Use case: ad verification
Ad verification proxies send a page load out from an address in the country, US state or US city you are checking. What an ad platform serves there is the platform's decision. Pick a country from 150 on Premium and Mobile, a US state on Essential and Premium, and a US city on Premium and Mobile. Rotate per check, or hold one IP to follow an ad to its landing page.
Ad verification proxies
Proxies for ad verification are proxies that ad-quality teams and tools send their page loads through, so each check comes from an IP in the place an ad is meant to run, not from your office. The proxy sets where the request leaves from; what the ad platform serves back is its own decision.
What you can check
The request leaves from an address in the country you pick, from 150 on Premium and Mobile. What the ad platform serves is its decision; you compare it with what the campaign was booked to run.
The request leaves from an address in the US state or US city you pick: any of the 51 US state targets on Essential and Premium, and a US city on Premium and Mobile.
Mobile exits are real phones on carrier networks, so the request leaves from a mobile network address.
Where teams start
Premium takes a country, a US state and a US city, and speaks SOCKS5 as well as HTTP. Mobile sends the request from a phone on a carrier network. Essential, from $1.50 per GB, covers a country or US state check when no US city is needed. All three are prepaid by the gigabyte with no subscription.
Cost control
Ad pages pull in many hosts. The Usage tab shows the gigabytes each domain used, live, so a verification run that loads heavy creative shows up on its own row before it shows up on a bill.
Acceptable use
Our Acceptable Use Policy permits advertising verification, brand-protection monitoring, and detection of ad fraud. It prohibits click or impression fraud, so load the ad and its landing page and leave the clicking to viewers. The rest of the policy still applies, and so does the law where you and your targets are.
Read the Acceptable Use PolicyDevelopers
HTTP on port 7777 on every pool. SOCKS5 on port 1080 on every pool except Essential. Country, session and session length live in the username, so there is no SDK to install and nothing to change in your code but one line.
About two minutes from sign-in to your first proxy.
Works with
$ curl -x premium.resifactory.net:7777 \
-U "you~us~k3n7~120:PASSWORD" \
https://api.ipify.org
203.0.113.42
# same session id, same exit
$ curl -x premium.resifactory.net:7777 \
-U "you~us~k3n7~120:PASSWORD" \
https://api.ipify.org
203.0.113.42import requests
user = "you~us~k3n7~120"
proxy = f"http://{user}:[email protected]:7777"
r = requests.get("https://api.ipify.org",
proxies={"http": proxy, "https": proxy})
print(r.text) # 203.0.113.42, held for the sessionimport { chromium } from "playwright";
const browser = await chromium.launch({
proxy: {
server: "http://premium.resifactory.net:7777",
username: "you~us~k3n7~120",
password: "PASSWORD",
},
});Same session id, same exit. 203.0.113.42 is a documentation address; yours will differ.
Change the string, not the code.
premium.resifactory.net:7777userlogin~uscountry~k3n7session id~120hold 120 minhost:port:user:passGET /pools lists the countries and US states each pool serves.A 3-month term is $10/mo less.