Certainly: Fastly’s Own TLS Certification Authority
This cached copy works for me:
https://archive.is/20230221154358/https://www.fastly.com/blo...
The original page is a 404 for me.
Hey! I'm on Fastly's DevX team. Sorry for the 404, we had to make some corrections so we took it down to republish it. But we're super thrilled to see the enthusiasm here and I'm passing along the feedback you shared too! Thanks everyone
I like this. We need to reduce our reliance on Let's Encrypt, so another CA which supports ACME is definitely welcome to me. The GoDaddy cross signature should make Certainly be accepted by just about any client.
Also, I really like the name :)
Accepted into the root stores for Mozilla, Apple, and Google, but what about Microsoft? (Or maybe Microsoft's doesn't matter anymore with Chrome using their own store since 105, Edge being a Chrome variant, and Firefox always having used their own?)
Though the intermediate cert is cross-signed by GoDaddy, so this isn't a problem right now.
It looks like Fastly started working on Certainly sometime before March 2019, because that’s when they filed a trademark application. [1]
Three years seems like a long time to be working on a CA!
Good for them for using ACME, but this appears to be some kind of add-on to Fastly, and not "here's my money, one signed cert, please" like I would expect from a general purpose CA
certainly 404
don't downvote me
maybe it was taken down, there is another post which made couple of minutes back
"Protecting your web apps has never been easier: Introducing the Fastly Managed Security Service" https://www.fastly.com/blog/protecting-your-web-apps-has-nev...
This appears to throw a 404 for me.
404, this seems to have been released by accident.
This is great! Any word on acme limits and quotas?
404 not found
Link is dead.
404
[Off-topic] but they've got absolutely bizarre webserver/blog behavior. I noticed "page not found" flash briefly on my screen before the content loaded, and indeed you can confirm with curl or network inspector it's actually returning http 404 status code/"page not found" content and then some bunch-o-JS injects the blog post. The Aristocrats!