Opened 5 years ago

Closed 5 years ago

#15159 closed enhancement (fixed)

Add meek support to ooni-probe

Reported by: dcf Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Keywords:
Cc: joelanders Actual Points:
Parent ID: #15170 Points:
Reviewer: Sponsor:


It would be nice if ooni-probe could test current and potential front domains used by meek. This could be as simple as doing an HTTPS fetch and seeing if it completes successfully, with the expected certificate. The idea is, that the most likely way for a censor to block meek is to block the front domain somehow.

The current list of fronts is:


Then, it would be good to test some potential future domain names, so we would know which ones are reachable in case we need to switch (like this mailing list post, What to do if meek gets blocked). For example,


It might be fun to test also the non-fronted domains, just in case a censor tried doing that:


Child Tickets

Change History (3)

comment:1 Changed 5 years ago by hellais

Parent ID: #15170

comment:2 Changed 5 years ago by dcf

Arturo pointed me to the upstream Citizen Lab test-lists repository from which ooniprobe gets its list of URLs. In one of the files is the list of Tor Browser bridges:

Arturo says that ooniprobe has logic to parse out the bridge lines and try connecting to Tor using each of them.

I found a recent bridge_reachability report:

However it doesn't contain the word "meek" (nor "flashproxy", nor "obfs4"). Am I looking in the wrong place?

The other domains I mentioned in the description, I plan to handle by submitting them to the upstream test-lists repository.

Last edited 5 years ago by dcf (previous) (diff)

comment:3 Changed 5 years ago by dcf

Resolution: fixed
Status: newclosed

The relevant URLs were merged upstream in

Note: See TracTickets for help on using tickets.