No, someone misconfigured our system to look like that though! Our DNS hosting is not in use for that domain (it is NOT delegated to us:
$ host -t soa docs.armory.io
docs.armory.io has no SOA record
)
…so you should remove it so our system works correctly. You can do that here:
Incorrect configuration of our DNS hosting when not used causes incorrect behavior with SSL such as what you’re seeing.
Once you do that, let me know and I can try to update the SSL certificate to include your preferred list of branch subdomains, assuming you have DNS setup (at AWS!) as mentioned in this article:
You’ll need to ping us with the list after it is configured, and we’ll be able to help get it in place for you in the cert.