# HTTPS forbidden on meta?

I often use a system that wants to block selective statements that I send out. Not sure why, but it's a work system, go figure... I've found that going to the site in HTTPS will prevent such filtering from occurring (I use my own devices so no custom root certificates installed). I tried to go to meta via HTTPS, and was told that it isn't allowed. Why is HTTPS allowed on the main site, but not on meta?

• So your company is doing DPI... That's very intrusive. More than a bug, I think this is a feature request. – Antzi Dec 23 '15 at 16:15
• It took me quite a while to realize what was happening myself... – PearsonArtPhoto Dec 23 '15 at 16:30
• HTTPS on meta is not supported right now. Unfortunately, we can get a certification for meta.*.stackexchange.com and we don't relish the idea of maintaining hundreds of certifications for per-site metas. There is a plan, but it's not exactly a top priority at the moment. – Jon Ericson Dec 23 '15 at 18:03
• meta.stackexchange.com/q/265918/155668 . Oh well, same site, but on meta.stackexchange... Sigh. – PearsonArtPhoto Dec 23 '15 at 18:42
• I have switched to the Emacs app for Stack Exchange. It works fine, and in fact I'm posting this comment via TLS API. – Deer Hunter Jan 12 '16 at 23:18