TLS, the Transport Layer Security protocol, has quickly become the most popular protocol on the Internet, already used to load over 70% of web pages in Mozilla Firefox. Due to its ubiquity, TLS is also a popular protocol for censorship circumvention tools, including Tor and Signal, among others. The problem was temporarily corrected by updating to Firefox 45, but only a few months later, meek was blocked again in the same manner, this time by the FortiGuard firewall, which identified a combination of SNI extension values sent by meek and otherwise matching the signature of Firefox 45 [22]. At that time, Firefox 47 had been released, supporting a distinguishable set of features. The rapid pace of new implementations and versions is a difficult task to keep up with. Another motivating example of these challenges is found in the Signal secure messaging application [57]. Until recently, Signal employed domain fronting to evade censorship in several countries including Egypt, Saudi Arabia, and the United Arab Emirates [25], [41]. However, due to a complicated interaction with the library it used to implement TLS, we find that Client Hello messages sent by Signal while domain fronting differ from their intended specification, ultimately allowing them to be distinguished from the implementations