First confirm the request used the proxy and record the exit IP, then check public WHOIS, ASN, or RDAP. That is a hint, not a certification. ZTProxy does not sell a separate checker product. Not for mainland China.
To judge whether an exit looks residential, first confirm the request actually used the proxy, record the exit IP, then compare public WHOIS, ASN, or RDAP data with the product you ordered in the console. This is a verification method—not a second definition page (see what is a residential proxy) and not the canonical residential vs datacenter chooser.
ZTProxy sells rotating residential (per GB) and static residential (per IP·month). There is no separate “residential checker” product or certification badge, and third-party reputation scores are not official results. Public registration data is only a hint: stale records, shared exits, or labeling errors can mislead. Not for mainland China. Authorized targets only.
Suggested order
- Using the host, port, and auth from the console, follow test with curl and send one HTTPS request to a page you may use that can show the request IP.
- Confirm that IP is not your machine’s current address; otherwise see 407 and timeouts before anything else.
- Look up the exit in public WHOIS / RDAP / ASN (a public registry you choose and are allowed to use). Read the org and network-type description.
- Compare country or region with the console order; if they disagree, check the order first—do not invent credential syntax.
- If the string itself may be wrong, see proxy format and HTTP / SOCKS5 setup.
The command below only shows a proxied request. Replace the target with a check URL you may use. Placeholders are not production hosts.
curl -sS --connect-timeout 20 --max-time 30 \
--proxy "http://proxy.example.invalid:10000" \
--proxy-user "USER_EXAMPLE:PASS_EXAMPLE_NOT_REAL" \
"https://example.com"
What each check can and cannot show
| Check | Often shows | Do not treat as |
|---|---|---|
| Proxied IP ≠ your machine IP | This request used the exit for those credentials | A “certified” residential exit, or a promise the IP never changes |
| Console product is rotating or static residential | You ordered a residential product we sell | That a third-party database will use the same label |
| Public WHOIS/ASN/RDAP leans broadband or access, not a typical cloud netblock | A hint of residential or access-network | Official certification, a fixed score, or “cannot be seen as a proxy” |
| Public data leans hosting / cloud / datacenter | A reason to re-check the product type and path | Proof of fraud; registries can lag |
| An address from a free public list | See risks in free vs paid residential | A verified residential pool |
Easy misreads
- A VPN is not the same as a proxy. A device tunnel can also exit on residential or datacenter space. See residential proxy vs VPN.
- We do not sell datacenter, mobile, or marketing-ISP SKUs. If public data looks mobile or ISP, do not infer those products exist here. See residential vs mobile and ISP vs residential.
- A sticky-session IP can change when the window ends, so one lookup does not describe the whole term. See sticky ≠ static.
- Do not treat a “proxy score” or a blacklist hit as an official ZTProxy result.
Compliance and scope
Verification is for confirming product type and path—not for bypassing site limits or faking an identity. Prices follow the console and pricing (rotating about $0.40/GB, about $0.20/GB on a 100 TB full bundle; static about $1.50 shared and about $5 dedicated per IP/month). USDT/USDC available; Visa/Mastercard in application. Not for mainland China.
FAQ
Do you offer an official residential-detection API?
No separate checker product. Use the console product type, your own connectivity check, and public registry data.
If WHOIS says broadband, is it 100% residential?
No. Public records lag and may not match routing perfectly. It is a hint, not a certificate.
If I see a cloud netblock, is the order wrong?
First confirm the request used that order’s credentials, then compare the console product type. Labeling errors exist, but a datacenter-like result is a reason to pause and check, not to ignore.
Do I have to look up every new IP on rotating residential?
A previous lookup only describes that address. If you need one exit to re-check over a term, static is the better fit.
Can I skip this and use a free proxy list?
Not recommended. Public nodes are often hard to verify. See free vs paid residential.
Does this prove I am anonymous?
No. Exit type is not anonymity. Accounts, browsers, and payload can still identify a visit.
Can I use the example host and password as-is?
No. Replace them with console values.
Where are prices confirmed?
In the console and on pricing.