Ad verification
Check placements and catch ad fraud through genuine local IPs.
Use case · Brand protection
Find counterfeit listings, phishing pages and unauthorized sellers that only reveal themselves to real customers in specific markets. Investigate from genuine residential and mobile IPs, and capture evidence that holds up.
The challenge
The problems every team in brand protection runs into sooner or later.
Phishing kits and counterfeit shops show harmless content to corporate networks, security vendors and datacenter IPs, and reveal the real page only to consumers in the targeted country.
Counterfeits and lookalike domains surface on regional marketplaces, local social platforms and country-specific search ads. Monitoring from one location leaves most of that activity out of view.
Registrars, hosts and marketplaces act faster on clear proof: what was shown, to whom, from where and when. Screenshots without that context are easy to dispute and slow to process.
The solution
Settings you control from the username, with no extra tooling or separate endpoints.
Residential and mobile IPs come from real consumer connections, so cloaked phishing and counterfeit pages are far more likely to show you what they show victims instead of a decoy.
Check each suspect URL from the countries where your customers buy, down to the city or network, and see regional marketplaces and local ads the way local shoppers do.
Pair every capture with the exit IP, location, timestamp and a SHA-256 hash of the response. A sticky session keeps the IP check and the capture on the same address.
Schedule recurring sweeps of marketplaces, search ads and newly registered lookalike domains. Rotation per request keeps long-running monitors steady and spreads them across many IPs.
Recommended
Start with the first one. Most teams add a second pool as their targets grow.
Get started
Gather suspect domains, marketplace listings, social profiles and search ads from monitoring tools and customer reports. Note the countries where each threat targets your customers.
Visit each suspect through gw.proxonym.com:8000 with the target country and a sticky session, using a desktop or mobile user agent that matches the likely victim.
Store the page, final URL, exit IP, timestamp and hash for every capture, then file takedown requests with registrars, hosts and marketplaces backed by consistent, verifiable evidence.
Best practices for brand protection
# pip install requests
import hashlib
import json
import pathlib
import secrets
from datetime import datetime, timezone
import requests
SUSPECTS = [ # lookalike domains and listings your team flagged
"https://examp1e-outlet.example/",
"https://example-support-login.example/",
]
COUNTRIES = ["us", "gb", "de"] # markets where your customers are targeted
BRAND = "example"
UA = ("Mozilla/5.0 (Linux; Android 14; Pixel 8) AppleWebKit/537.36 "
"(KHTML, like Gecko) Chrome/129.0 Mobile Safari/537.36")
OUT = pathlib.Path("evidence")
OUT.mkdir(exist_ok=True)
for url in SUSPECTS:
for cc in COUNTRIES:
# Sticky session: the IP check and the capture leave from the same exit IP
user = f"USERNAME-country-{cc}-session-{secrets.token_hex(4)}"
proxy = f"http://{user}:PASSWORD@gw.proxonym.com:8000"
proxies = {"http": proxy, "https": proxy}
try:
exit_ip = requests.get("https://api.ipify.org", proxies=proxies, timeout=20).text
r = requests.get(url, headers={"User-Agent": UA}, proxies=proxies, timeout=30)
except requests.RequestException as exc:
print(cc, url, "error:", exc)
continue
digest = hashlib.sha256(r.content).hexdigest()
(OUT / f"{digest}.html").write_bytes(r.content)
record = {"url": url, "final_url": r.url, "country": cc, "exit_ip": exit_ip,
"status": r.status_code, "sha256": digest,
"captured_at": datetime.now(timezone.utc).isoformat(),
"mentions_brand": BRAND in r.text.lower()}
with open(OUT / "log.jsonl", "a", encoding="utf-8") as log:
log.write(json.dumps(record) + "\n")
print(cc, r.status_code, record["mentions_brand"], r.url)FAQ
Still unsure? The help center answers billing, setup and account questions.
Open the help centerMany phishing kits and counterfeit shops filter visitors and show harmless content to corporate networks, security vendors and datacenter IPs. Residential and mobile IPs belong to real consumer connections in the targeted country, so you are far more likely to see the real page and capture it as evidence.
Yes. Change -country- in the username to view each regional marketplace from inside the market, or add -city- for local listings. Rotation per request spreads large monitoring runs across many IPs, while sticky sessions of up to 120 minutes keep multi-page investigations consistent.
Open a sticky session, record the exit IP with a check such as api.ipify.org, then capture the page through the same session. Store the raw response with a UTC timestamp, the final URL after redirects and a SHA-256 hash, so anyone can verify the file later.
A proxy hides your corporate IP from the operator, but it does not protect the device you browse from. Use an isolated environment, never submit real credentials or payment details and avoid downloading files. Treat every suspect page as hostile and keep investigations apart from production systems.
Viewing publicly accessible pages to document infringement is a routine part of brand enforcement. Stay passive: do not log in under false identities, buy suspected counterfeits or interfere with the sites unless your legal counsel approves the approach. File takedowns through registrars, hosts and marketplaces.
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 brand protection on the same account.
Check placements and catch ad fraud through genuine local IPs.
Track competitor prices, stock and reviews across marketplaces.
Run multiple accounts on stable, trusted mobile and ISP IPs.
Pick a plan, pay with crypto and send your first request through Proxonym in minutes.