1. General Results, most used to calculate the result A name "nexgentents.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 51456 (complete: 129392) A Good: All ip addresses are public addresses Warning: Only one ip address found: nexgentents.com has only one ip address. Warning: Only one ip address found: www.nexgentents.com 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: nexgentents.com 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.nexgentents.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A https://162.241.217.75/ 162.241.217.75 https://nexgentents.com/404.html Correct redirect https to https A Good: destination is https A Good - only one version with Http-Status 200 A Good: one preferred version: non-www is preferred A Good: No cookie sent via http. 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) A http://nexgentents.com/ 162.241.217.75 https://nexgentents.com/ Correct redirect http - https with the same domain name A http://www.nexgentents.com/ 162.241.217.75 https://www.nexgentents.com/ Correct redirect http - https with the same domain name B https://nexgentents.com/ 162.241.217.75 Missing HSTS-Header B https://www.nexgentents.com/ 162.241.217.75 Missing HSTS-Header M https://nexgentents.com/404.html Misconfiguration - main pages should never send http status 400 - 499 N https://162.241.217.75/ 162.241.217.75 https://nexgentents.com/404.html Error - Certificate isn't trusted, RemoteCertificateNameMismatch N nexgentents.com:993 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N nexgentents.com:995 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N www.nexgentents.com:993 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N www.nexgentents.com:995 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 162.241.217.75:993 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 162.241.217.75:995 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 162.241.217.75:2083 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 162.241.217.75:2087 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N 162.241.217.75:2096 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain nexgentents.com, 1 ip addresses. 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.nexgentents.com, 1 ip addresses. 2. Header-Checks 3. DNS- and NameServer - Checks A Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 9 Queries complete, 5 with IPv6, 4 with IPv4. Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses. Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: ns1.bluehost.com, ns2.bluehost.com, 2 Name Servers included in Delegation: ns1.bluehost.com, ns2.bluehost.com, 2 Name Servers included in 1 Zone definitions: ns1.bluehost.com, ns2.bluehost.com, 1 Name Servers listed in SOA.Primary: ns1.bluehost.com. A Good: Only one SOA.Primary Name Server found.: ns1.bluehost.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1.bluehost.com. 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: ns1.bluehost.com, ns2.bluehost.com 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 Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 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: com 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: bluehost.com Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: CA A Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 162., 1 different subnets (first two Bytes): 162.159., 2 different subnets (first three Bytes): 162.159.24., 162.159.25. A Good: Name Server IPv4-addresses from different subnet found: A Good: Nameserver supports TCP connections: 2 good Nameserver A Good: Nameserver supports Echo Capitalization: 2 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 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 to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries. 4. Content- and Performance-critical Checks A Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://nexgentents.com/ 162.241.217.75 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://nexgentents.com/ 162.241.217.75 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. https://nexgentents.com/ 162.241.217.75 Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 11 script elements without defer/async. https://nexgentents.com/404.html Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 10 script elements without defer/async. A Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 40 external CSS / JavaScript files found A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 14 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 38 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 2 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 40 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 23 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 23 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: Some img-elements have a valid alt-attribute.: 9 img-elements found, 6 img-elements with correct alt-attributes (defined, not an empty value). Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 3 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found. 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://nexgentents.com/404.html 4.157 seconds Warning: 404 needs more then one second A Duration: 233610 milliseconds, 233.610 seconds