It should be fixed now - https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/5b5f5a.... Edward Dore Freethought Internet On 30/07/2018, 19:47, "Outages on behalf of Edward Dore via Outages" <outages-bounces@outages.org on behalf of outages@outages.org> wrote: whois.enom.com is showing the letsencrypt.org domain as having the "clienthold" status, which means that it has been pulled from DNS. This can be billing related, abuse or legal dispute etc. The domain looks to be registered through eNom via Namecheap, so I've asked someone at Namecheap to take a look. Edward Dore Freethought Internet On 30/07/2018, 19:39, "Outages on behalf of Chris Adams via Outages" <outages-bounces@outages.org on behalf of outages@outages.org> wrote: The domain for Let's Encrypt, letsencrypt.org, appears to have been dropped from the .org servers (whois is not showing it as expired). This is causing problems for things that try to check CRLs because the Let's Encrypt CRL servers don't resolve. -- Chris Adams <cma@cmadams.net> _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages