It should be fixed now -
https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/5b5f5aa93a343f54d7982864.
Edward Dore
Freethought Internet
On 30/07/2018, 19:47, "Outages on behalf of Edward Dore via Outages"
wrote:
whois.enom.com is showing the letsencrypt.org domain as h
Hi,
On Mon, Jul 30, 2018 at 01:39:36PM -0500, Chris Adams via Outages 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
PM
> To: outages@outages.org
> Subject: [outages] Let's Encrypt DNS broken
>
> 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
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
Domain is working for me
Name:letsencrypt.org
Addresses: 2001:559:13:19e::ce0
2001:559:13:19b::ce0
96.6.95.26
On Mon, Jul 30, 2018 at 12:39 PM, Chris Adams via Outages <
outages@outages.org> wrote:
> The domain for Let's Encrypt, letsencrypt.org, appears to have been
> d
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
_
