← Back to context

Comment by martinclayton

2 months ago

Seems Let's Encrypt also have control of https://letsdecrypt.org.

It takes you to https://www.nsa.gov rather than Let's Encrypt.

Not sure what to make of that!

letsdecrypt.org doesn't load for me.

  • Here's a curl from my connection:

       $ curl -v letsdecrypt.org
       * Host letsdecrypt.org:80 was resolved.
       * IPv6: (none)
       * IPv4: 62.116.130.8
       *   Trying 62.116.130.8:80...
       * Connected to letsdecrypt.org (62.116.130.8) port 80
       * using HTTP/1.x
       > GET / HTTP/1.1
       > Host: letsdecrypt.org
       > User-Agent: curl/8.14.1
       > Accept: */*
       > 
       * Request completely sent off
       < HTTP/1.1 301 Moved Permanently
       < Server: nginx
       < Date: Wed, 10 Dec 2025 15:20:48 GMT
       < Content-Type: text/html; charset=UTF-8
       < Transfer-Encoding: chunked
       < Connection: keep-alive
       < X-Redirector-ID: 14c2d856bcd2de3beae30791793b40ae43db49fc9ea482a825177a36e20108c4
       < Location: http://www.nsa.gov/
       < IX-Cache-Status: MISS
       < 
       * Connection #0 to host letsdecrypt.org left intact
    

    Seems to be hosted by InterNetX GmbH.

    Edit: Ah, over HTTPS protocol it doesn't respond.

       $ curl -v https://letsdecrypt.org
       * Host letsdecrypt.org:443 was resolved.
       * IPv6: (none)
       * IPv4: 62.116.130.8
       *   Trying 62.116.130.8:443...
    

    Web browsers that add it automatically probably get stuck.