# Tor Bridges This endpoint returns IP addresses for known **Tor bridges**, which are designed to help users in censored regions access the Tor network. These bridges are deliberately harder to discover and may not always be complete or public. **Endpoint:**\ `https://api.elliott.diy/v1/tor/obfs4` Currently, only **obfs4** bridges are supported. *** ### Response Format * **Plaintext (default)**\ Each bridge IP on a new line: ``` https://api.elliott.diy/v1/tor/obfs4 ``` * **JSON**\ Add `?format=json` to receive a structured object: ``` https://api.elliott.diy/v1/tor/obfs4?format=json ``` ```json { "ips": [ "x.x.x.x", "y.y.y.y" ] } ``` *** ### Access Restrictions Due to the sensitive nature of bridge relays, this endpoint is **restricted** by default. Bridges are a critical tool for bypassing censorship in oppressive regimes, and I avoid contributing to bridge enumeration that could block access for vulnerable users. If you have a legitimate use case (e.g., research, censorship circumvention, threat intel), contact me via email or any listed method on [elliott.diy](https://elliott.diy) to request access. *** ### Notes * Only obfs4 bridges are currently supported. * Data is curated and not guaranteed to be comprehensive. * Intended for responsible use only. * Cache is refreshed every 6 hours. --- # Agent Instructions: 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: ``` GET https://docs.elliott.diy/tor-recon/tor-bridges.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.