When checking to see if there is a meta for stackapps.com I found out that there is none (and a different Panda photo than I'm used to seeing). Also there's an SSL certificate error. This is probably a low priority or curiosity, but I thought I'd mention it. Previously such problems have been described as an oversight, and corrected.
Similar to the question: "Stacksnippets has the incorrect SSL certificate :(" I am reporting what seems to be described by Qualys as: "The domain name is an alias for a web site whose main name is different, but the alias was not included in the certificate by mistake.". The main site comes back as "A+" for four separate IP addresses.
When cleverly redirecting the errant URL it leads to a webpage that apparently could have been (but wasn't) included in the certificate. The Qualys test URL is here, for what it's worth to include it in the question (security report). Google, for example, doesn't do this clever trick; if I try to visit nosuchplace.google.com my browser simply says it can't connect, Google doesn't bother redirecting such errant URLs.
Perhaps it would be cost saving (for certificates) and easier to maintain if the redirection was to a webpage on the main site (for example) explaining that some sites don't have an associated meta site.
Note: The Q&A: "Wildcard SSL Cert producing error on Facebook.Stackoverflow.com" (from 2012) is marked as a dupe of a duplicate: "Network-wide HTTPS: It's time" which says https works network-wide. Thus, I feel this report is not a duplicate of that Q&A; and worth mentioning.