Fails on a new internal-style domain
Likely causes
- - The name collides with a new gTLD
- - Local resolver hijacks the name
Verified remedy
Use the real public hostname, or resolve remotely through the endpoint (SOCKS5 hostname form).
Proxy troubleshooting
Ranked causes, ordered diagnostics, and a verified remedy for err_icann_name_collision through a proxy - ending with a final connection check.
Quick answer
Fix: ERR_ICANN_NAME_COLLISION while using a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Ranked causes, ordered diagnostics, and a verified remedy for err_icann_name_collision through a proxy - ending with a final connection check.
Fix: ERR_ICANN_NAME_COLLISION while using a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Likely causes
Verified remedy
Use the real public hostname, or resolve remotely through the endpoint (SOCKS5 hostname form).
The action completes and the exit IP matches the endpoint.
If curl also fails, the endpoint is unhealthy: swap to a spare.
Facts last reviewed 2026-09-01.
Keep one profile on one static endpoint, verify exit IPs daily, and rotate credentials on a documented schedule.
Work the diagnosis tree top to bottom, confirm endpoint values, test with curl through the endpoint, then run the final connection check.
Buy self-serve now, or talk with us about a larger agency inventory.