> For the complete documentation index, see [llms.txt](https://docs.proxyshard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxyshard.com/eng/our-products/about-udp.md).

# About the UDP protocol

### **Contents**

* [How WebRTC detection works](/eng/our-products/about-udp/how-webrtc-leak-works.md)
* [How to check for WebRTC leaks or WebRTC functionality](/eng/our-products/about-udp/webrtc-leak-check-tools.md)
* [Why a TCP proxy alone is not enough!](/eng/our-products/about-udp/why-tcp-proxy-not-enough.md)
* [Software solutions for enabling WebRTC](/eng/our-products/about-udp/webrtc-software-solutions.md)
* [Why blocking WebRTC does not protect you from detection](/eng/our-products/about-udp/why-blocking-webrtc-doesnt-help.md)
* [Results of our field tests](/eng/our-products/about-udp/field-test-results.md)
* [FAQ](/eng/questions-and-answers/faq.md)

### **Introductory theory**

Modern anti-fraud systems are becoming increasingly persistent in identifying your real address or detecting the use of tools that hide your address. Even if you use a proxy or <mark style="color:purple;">VPN</mark>, they can determine that you are not a “real” user by many parameters.

One of the most common detection mechanisms is <mark style="color:purple;">WebRTC</mark>, a technology that can send requests around the proxy and therefore expose your real IP if <mark style="color:purple;">WebRTC</mark> is not blocked by the browser.<br>

The solution? Two-way <mark style="color:purple;">UDP</mark> protocol support in both proxies and software products.

{% hint style="info" %} <sup>*This article was inspired by*</sup> [<sup>*Zl0yTeam*</sup>](https://t.me/Zl0yTeam)<sup>\_ and their article\_</sup> [<sup>*“Why UDP proxies are needed and what WebRTC has to do with it”*</sup>](https://telegra.ph/Zachem-nuzhny-proksi-s-UDP-i-pri-chyom-tut-protechka-WrbRTC-v-Antike-12-19)<sup>*.*</sup>\ <sup>*It helped us significantly understand how*</sup><sup>*&#x20;*</sup><sup>*<mark style="color:purple;">WebRTC</mark>*</sup><sup>*&#x20;*</sup><sup>*works and write this article!*</sup>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.proxyshard.com/eng/our-products/about-udp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.