Browsers cannot independently set the HTTP Host header or TLS SNI field, blocking the standard censorship-trigger methods used in Geneva training. The paper proposes two workarounds: (1) keyword-based HTTP censorship triggers using forbidden strings in URL parameters, limited to censors that employ keyword filtering; and (2) registering domains whose strings contain a censored substring to exploit censor overblocking via overbroad regular expressions (e.g., registering a domain matching torproject.org's regex to also catch mentorproject.org).
From 2023-tran-crowdsourcing — Crowdsourcing the Discovery of Server-side Censorship Evasion Strategies
· §3 Design — Triggering Censorship
· 2023
· Free and Open Communications on the Internet
Implications
Test whether a target censor uses regex-based domain blocking; if so, overblocking domains are a reliable, no-SNI-control mechanism for triggering and studying censor behavior from browser clients.
Keyword-based trigger coverage is fundamentally limited — build fallback infrastructure for ASNs where keyword filtering is absent and overblocking domains cannot be registered.