1. General Results, most used to calculate the result A name "nasdoury.ovh" is domain, public suffix is "ovh", top-level-domain-type is "generic", tld-manager is "OVH SAS" A good: All ip addresses are public addresses Warning: Only one ip address found: nasdoury.ovh has only one ip address. Warning: Only one ip address found: www.nasdoury.ovh has only one ip address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: nasdoury.ovh has no ipv6 address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.nasdoury.ovh has no ipv6 address. A good: No asked Authoritative Name Server had a timeout A good: destination is https HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. A Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (5 urls) https://nasdoury.ovh/ 45.13.104.180 Url with incomplete Content-Type - header - missing charset https://www.nasdoury.ovh/ 45.13.104.180 Url with incomplete Content-Type - header - missing charset https://nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Url with incomplete Content-Type - header - missing charset https://www.nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Url with incomplete Content-Type - header - missing charset https://45.13.104.180/ 45.13.104.180 Url with incomplete Content-Type - header - missing charset A http://nasdoury.ovh/ 45.13.104.180 https://nasdoury.ovh/ correct redirect http - https with the same domain name A http://www.nasdoury.ovh/ 45.13.104.180 https://www.nasdoury.ovh/ correct redirect http - https with the same domain name B https://nasdoury.ovh/ 45.13.104.180 Missing HSTS-Header B https://www.nasdoury.ovh/ 45.13.104.180 Missing HSTS-Header B https://45.13.104.180/ 45.13.104.180 Missing HSTS-Header C Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version. C Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200. N https://nasdoury.ovh/ 45.13.104.180 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://45.13.104.180/ 45.13.104.180 Error - Certificate isn't trusted, RemoteCertificateNameMismatch Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain nasdoury.ovh, 1 ip addresses, 1 different http results. Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.nasdoury.ovh, 1 ip addresses, 1 different http results. 2. DNS- and NameServer - Checks A Info:: 2 different Name Servers found: dns100.ovh.net, ns100.ovh.net, 2 Name Servers included in Delegation: dns100.ovh.net, ns100.ovh.net, 2 Name Servers included in 1 Zone definitions: dns100.ovh.net, ns100.ovh.net, 1 Name Servers listed in SOA.Primary: dns100.ovh.net. A Good: Only one SOA.Primary Name Server found.: dns100.ovh.net. A Good: SOA.Primary Name Server included in the delegation set.: dns100.ovh.net. A Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: dns100.ovh.net, ns100.ovh.net A Good: All Name Server Domain Names have a Public Suffix. A Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address. A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found A Good: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: net Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: ovh.net Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR A Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.251., 2 different subnets (first three Bytes): 213.251.128., 213.251.188. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:1990:, 2001:41d0:0001:4a90: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 4 good Nameserver A Good: Nameserver supports Echo Capitalization: 4 good Nameserver X Nameserver Timeout checking Echo Capitalization: f.ext.nic.fr A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver Nameserver doesn't pass all EDNS-Checks: a.nic.fr: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: d.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (dns.fra.nic.fr). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok. 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 to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries. 3. Content- and Performance-critical Checks https://www.nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://nasdoury.ovh/ 45.13.104.180 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://www.nasdoury.ovh/ 45.13.104.180 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://www.nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://45.13.104.180/ 45.13.104.180 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://nasdoury.ovh/ 45.13.104.180 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.nasdoury.ovh/ 45.13.104.180 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.nasdoury.ovh/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://45.13.104.180/ 45.13.104.180 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. A Good: Every https connection via port 443 supports the http/2 protocol via ALPN. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Info: No img element found, no alt attribute checked 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 A Duration: 122743 milliseconds, 122.743 seconds