A name "dominioproyectos.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services" A good: All ip addresses are public addresses A good: No asked Authoritative Name Server had a timeout A Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) C Error - no version with Http-Status 200 H fatal error: No https - result with http-status 200, no encryption M https://dominioproyectos.com:3000/noticias/obtenernoticias 18.216.14.190 404 Misconfiguration - main pages should never send http status 400 - 499 M https://www.dominioproyectos.com:3000/noticias/obtenernoticias 18.216.14.190 404 Misconfiguration - main pages should never send http status 400 - 499 N https://dominioproyectos.com:3000/noticias/obtenernoticias 18.216.14.190 404 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://www.dominioproyectos.com:3000/noticias/obtenernoticias 18.216.14.190 404 Error - Certificate isn't trusted, RemoteCertificateChainErrors A Good: Nameserver supports TCP connections: 8 good Nameserver A Good: Nameserver supports Echo Capitalization: 8 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver A Good: All SOA have the same Serial Number Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization http://dominioproyectos.com:3000/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.216.14.190 -8 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. http://www.dominioproyectos.com:3000/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.216.14.190 -8 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. A Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx https://dominioproyectos.com:3000/noticias/obtenernoticias 18.216.14.190 404 4.013 seconds Warning: 404 needs more then one second https://www.dominioproyectos.com:3000/noticias/obtenernoticias 18.216.14.190 404 3.787 seconds Warning: 404 needs more then one second A Duration: 58680 milliseconds, 58.680 seconds