> For the complete documentation index, see [llms.txt](https://docs.shieldproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shieldproxies.com/using-your-proxies/test-your-proxies.md).

# Test Your Proxies

Test whether your proxies are connecting successfully using a proxy testing tool.

Testing a proxy before using it in production helps confirm whether the connection is working and whether the proxy format is accepted by the tester.

The current Shield Proxies documentation references these testers:

* [FOGLDN Proxy Tester](https://www.fogldn.com/proxy-tester/)
* [IPRoyal Proxy Tester](https://iproyal.com/proxy-tester/)

A successful result confirms that the tester was able to connect through the proxy. It does **not** guarantee that every target website, browser, bot, scraper or application will accept the same traffic.

A failed result means the proxy, credentials, format, protocol, authentication or network connection should be investigated further.

{% hint style="info" %}
If the tester succeeds but your real target or application fails, follow [Proxy Works in Tester but Not in App or Site](https://docs.shieldproxies.com/troubleshooting/proxy-works-in-tester-but-not-in-app-or-site.md) rather than assuming the proxy is dead.
{% endhint %}

## If a test fails

* [Proxies Not Working](https://docs.shieldproxies.com/troubleshooting/proxies-not-working.md)
* [Common Proxy Errors](https://docs.shieldproxies.com/troubleshooting/common-proxy-errors.md)
* [High Proxy Latency](https://docs.shieldproxies.com/troubleshooting/high-proxy-latency.md)
* [Open a Support Ticket](https://docs.shieldproxies.com/support-and-community/open-support-ticket.md)

When reporting an issue to support, include the affected proxy or ISP Order/Transaction ID, product, protocol, error, target, tester result and when the issue started. Do not post live proxy credentials in public Discord channels.
