Brand protection
Find counterfeits and phishing hidden behind geo-blocks.
Use case · Ad verification
Check every placement, redirect and landing page from genuine consumer connections in the markets you pay for. Catch cloaking, hijacked links and wrong creatives before they drain your budget.
The challenge
The problems every team in ad verification runs into sooner or later.
Ad servers pick creatives, landing pages and offers by country, city, carrier and device. A check from your office shows one combination out of the hundreds your campaign actually serves.
Cloaking scripts show a clean page to datacenter IPs and known verification ranges, then send real users to scams or unsafe content. Only a genuine consumer connection shows you the truth.
Disputes with networks and publishers need evidence: where the ad ran, what it showed, where the click went and when. One screenshot from one location does not hold up across markets.
The solution
Settings you control from the username, with no extra tooling or separate endpoints.
Check placements from residential IPs in 195+ countries, down to the city or ASN. You see the same creative and landing page that a real user in that market receives.
Add -type-mobile to route checks through 3G/4G/5G carrier IPs in the United States, United Kingdom and Austria, and catch redirects that only trigger on mobile networks.
Follow every hop from the tracking link to the final landing page on one sticky IP. Spot unexpected domains, hijacked affiliate parameters and broken links before they cost you budget.
Residential IPs come from people who opted in and can opt out at any time. Your checks look like ordinary visits, which makes them much harder for cloaking scripts to single out.
Recommended
Start with the first one. Most teams add a second pool as their targets grow.
Get started
Collect the tracking links, publishers and geos you pay for. Decide which checks need mobile carrier IPs and which can run on residential IPs.
Request each link through gw.proxonym.com:8000 with the market in the username and a sticky session, using a desktop or mobile user agent that matches the placement.
Save the redirect chain, final URL, screenshot and timestamp for each market. Flag unexpected domains, missing creatives and mismatched offers, then share the evidence with partners.
Best practices for ad verification
# pip install requests
import secrets
import requests
AD_URL = "https://ads.example.com/click?campaign=spring-sale" # your tracking link
EXPECTED = "https://www.example.com/spring-sale" # intended landing page
MARKETS = ["us", "gb", "de", "fr", "br"]
MOBILE_UA = ("Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 "
"(KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1")
for cc in MARKETS:
# One sticky session per market: every hop of the chain uses the same IP.
# For carrier IPs (US, GB, AT) add -type-mobile and keep -lifetime- at 3 or less.
user = f"USERNAME-country-{cc}-session-{secrets.token_hex(4)}"
proxy = f"http://{user}:PASSWORD@gw.proxonym.com:8000"
r = requests.get(AD_URL, headers={"User-Agent": MOBILE_UA}, timeout=30,
proxies={"http": proxy, "https": proxy})
hops = " > ".join(str(h.status_code) for h in r.history + [r])
verdict = "OK" if r.url.startswith(EXPECTED) else "CHECK"
print(f"{cc} {verdict:<5} {hops} final: {r.url}")
for h in r.history:
print(f" {h.status_code} -> {h.headers.get('Location')}")FAQ
Still unsure? The help center answers billing, setup and account questions.
Open the help centerAd servers and fraudsters both treat datacenter IPs differently from consumer traffic. Residential IPs belong to real home connections, so you receive the same creatives, redirects and landing pages that real users get, including the ones a cloaking script would hide from a known verification range.
Yes. Add -type-mobile to your username to route through 3G/4G/5G carrier IPs in the United States, United Kingdom and Austria, with more countries rolling out. Mobile proxies rotate per connection and support sticky sessions of up to 3 minutes, which is enough for a full redirect chain.
Add -city- with a lowercase name and underscores for spaces, for example USERNAME-country-us-city-new_york. Use -state- for a wider area, or -asn- to target a network, such as -asn-7922 for Comcast, when a campaign is aimed at the customers of a specific ISP.
From the ad server's point of view, each check is a real impression or click. Keep volumes proportionate to the campaign, filter your verification traffic out of analytics where you can identify it and agree on a testing approach with partners before running a large audit.
Yes. Checking how your own ads and paid placements appear is standard practice for advertisers, agencies and ad networks. Respect the terms of the platforms involved and keep check volumes reasonable. Generating fake clicks or impressions is abuse, not verification, and our acceptable use policy applies to all traffic.
Platforms
Platform guides with targeting tips, ready-to-run code and the proxy types that work best on each site.
Related
Teams often combine these with ad verification on the same account.
Find counterfeits and phishing hidden behind geo-blocks.
Run multiple accounts on stable, trusted mobile and ISP IPs.
See rankings and ads exactly as searchers do, from any city.
Pick a plan, pay with crypto and send your first request through Proxonym in minutes.