bad or no domain certificate

[Meinte Boersma]

Both http://mbeddr.com (upgraded to/forwarded to HTTPS) and https://mbeddr.com produce "connection not secure" warnings, possibly because of a bad certificate? I have people asking about whether they should be accessing anything on these domains at all. In particular, I have a link (http://mbeddr.com/files/gc-sle.pdf) in my upcoming DSL book (https://www.manning.com/books/building-user-friendly-dsls) to which this applies.

Is there any way this domain can be made to jump through the necessary hoops?