https://onionoo.torproject.org/details?lookup=$hashed_fingerprint
https://bridges.torproject.org/status?id=$hashed_fingerprint
May someone explain to me, what happens in the background? When and why are bridges (especially webtunnel) shown on bridges.torproject.org
Some of my (Docker)-bridges do not show up on bridges.torproject.org “no resources for the given id” but are present on onionoo.torproject.org
What I have learned so far, is that all bridges report their existence to the Bridge Authority (see Serge and previously Bifroest/Tonga).
Its sanitized descriptors are published and may be found here: collector.torproject.org and can be searched “easily” with Onionoo.
Before October 2024 the non-sanitized descriptors where sent to BridgeDB which is now superseded by Rdsys.
Before handing out Bridges to the user they get regular testing by bridgestrap. Results are eventually published at https://bridges.torproject.org/status?id=$hashed_fingerprint and may also be found here: collector.torproject.org.
So if you set up a bridge and it is working for you, but not published at https://bridges.torproject.org/status?id=$hashed_fingerprint, you can hopefully investigate what seems to be the issue…
Finally a bridge gets assigned to a pool and gets a distribution method assigned (if not set in torrc to a specific distribution). This may be checked here: collector.torproject.org.