1. General Results, most used to calculate the result A name "chase.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: 52208 (complete: 131120) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: chase.com has 7 different ip addresses (authoritative). Warning: Only one ip address found: www.chase.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: chase.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.chase.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A https://www.chase.com/resources/404.html https://www.chase.com/digital/resources/oops.html Correct redirect https to https A https://www.chase.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de https://www.chase.com/index.html.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Correct redirect https to https A https://www.chase.com/index.html.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de https://www.chase.com/resources/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: 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://www.chase.com/ 159.53.42.11 https://www.chase.com/ Correct redirect http - https with the same domain name A http://www.chase.com/ 159.53.85.137 https://www.chase.com/ Correct redirect http - https with the same domain name B https://chase.com/ 159.53.42.11 Missing HSTS-Header B https://chase.com/ 159.53.44.60 Missing HSTS-Header B https://chase.com/ 159.53.84.126 Missing HSTS-Header B https://chase.com/ 159.53.85.137 Missing HSTS-Header B https://chase.com/ 159.53.113.168 Missing HSTS-Header B https://chase.com/ 159.53.116.62 Missing HSTS-Header B https://chase.com/ 159.53.224.21 Missing HSTS-Header B https://www.chase.com/ 159.53.42.11 TS01afb5d0=01bafcdf863adfe889389a776ca8e1a68181fda2710c26c2ef2fdaa2edf88b2fe6712074d285a2fd37421b37f7bb93a011a28a9436; Path=/ Cookie sent via https, but not marked as secure B https://www.chase.com/ 159.53.85.137 TS01afb5d0=0162ca7a3d09120843cd0987a67e338dc6817b0263fe9150fd40a557166cd1b5d8f102f5b890b31fa418354be2b20d08c64b03236b; Path=/ Cookie sent via https, but not marked as secure B https://www.chase.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de TS01afb5d0=01c8192421fb1c14c04bff483238101d391040b758234153074b78af17e07f0db159cece12bc61f4903f40d2b5c001ec27c5c19834; Path=/ Cookie sent via https, but not marked as secure B https://www.chase.com/index.html.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de TS01afb5d0=01c819242160cde32001814f6bd0c798da546d1e9d3134a0cb6773c11dabfadef084bd5f449a13728edd8875366952e2017b7e8d3e; Path=/ Cookie sent via https, but not marked as secure B https://www.chase.com/resources/404.html TS01afb5d0=01c81924216611e8c45758966998132588d0d0a77e2886391a4acd18c1686e73650121c6af19fae2c1b5dc5a4e4acde13a13f9b400; Path=/ Cookie sent via https, but not marked as secure B https://www.chase.com/digital/resources/oops.html TS01afb5d0=01bde6ad2190c613bf8cde062f743d001d18aaae79595966c6a507d6276e11640d10e46682f735ff4e6333d1319bc67be5b3429ebe; Path=/ Cookie sent via https, but not marked as secure B https://www.chase.com/ 159.53.42.11 TS01afb5d0=01bafcdf863adfe889389a776ca8e1a68181fda2710c26c2ef2fdaa2edf88b2fe6712074d285a2fd37421b37f7bb93a011a28a9436; Path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/ 159.53.42.11 ppnet_2777=!81KQH3MrdhqiubZTxUapzyaCI1H4L/9y55Kg9Q7orBVEmWJWvhNB+ZLx84r8hH+ulNP+bTP+WLj+zA==; path=/; Httponly; Secure Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/ 159.53.85.137 TS01afb5d0=0162ca7a3d09120843cd0987a67e338dc6817b0263fe9150fd40a557166cd1b5d8f102f5b890b31fa418354be2b20d08c64b03236b; Path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/ 159.53.85.137 ppnet_2777=!AzN/1Rw1KY9hnDXxR9usC9w7H6fJpQSvdmkw10zN5fQFwR7Lq26SQW3O7ngy+59z80WHm8rKU4PX8Yg=; path=/; Httponly; Secure Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de TS01afb5d0=01c8192421fb1c14c04bff483238101d391040b758234153074b78af17e07f0db159cece12bc61f4903f40d2b5c001ec27c5c19834; Path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de ppnet_2777=!b8QDitOOXYQd023SdwumPgyvqQhhBnxrkqF6EAosCNkfwlnzxANuEGO/YubuOBIXvMflwSSJ1rZHWA==; path=/; Httponly; Secure Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/index.html.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de TS01afb5d0=01c819242160cde32001814f6bd0c798da546d1e9d3134a0cb6773c11dabfadef084bd5f449a13728edd8875366952e2017b7e8d3e; Path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/index.html.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de ppnet_2777=!R1IMjEvh+nEnw4/SdwumPgyvqQhhBvcijW1apB+IIJemGtXR3TPCXP8HiLWkK5yEEwYIJlg9J26k/Q==; path=/; Httponly; Secure Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/resources/404.html TS01afb5d0=01c81924216611e8c45758966998132588d0d0a77e2886391a4acd18c1686e73650121c6af19fae2c1b5dc5a4e4acde13a13f9b400; Path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/resources/404.html ppnet_2777=!hy0iwrKOPFb0mX3SdwumPgyvqQhhBvVYma/wXkVJGo2Y0MuH4gC5ER5YV4bb5jyx1rZJ73gZJO9gAA==; path=/; Httponly; Secure Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/digital/resources/oops.html TS01afb5d0=01bde6ad2190c613bf8cde062f743d001d18aaae79595966c6a507d6276e11640d10e46682f735ff4e6333d1319bc67be5b3429ebe; Path=/ Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.chase.com/digital/resources/oops.html ppnet_2777=!7fopIJAFGXzg55vSdwumPgyvqQhhBpBxfhWWGJezfQ9Xcnh8x2gShWZQPZdAL864MY3kMc5iZoy+2Q==; path=/; Httponly; Secure Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. E http://chase.com/ 159.53.42.11 https://www.chase.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://chase.com/ 159.53.44.60 https://www.chase.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://chase.com/ 159.53.84.126 https://www.chase.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://chase.com/ 159.53.85.137 https://www.chase.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://chase.com/ 159.53.113.168 https://www.chase.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://chase.com/ 159.53.116.62 https://www.chase.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://chase.com/ 159.53.224.21 https://www.chase.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. I https://www.chase.com/ 159.53.85.137 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. I https://www.chase.com/ 159.53.42.11 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. I https://www.chase.com/digital/resources/oops.html Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. N https://159.53.42.11/ 159.53.42.11 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://159.53.44.60/ 159.53.44.60 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://159.53.84.126/ 159.53.84.126 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://159.53.85.137/ 159.53.85.137 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://159.53.113.168/ 159.53.113.168 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://159.53.116.62/ 159.53.116.62 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://159.53.224.21/ 159.53.224.21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain chase.com, 7 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain chase.com, 7 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.chase.com, 1 ip addresses, 1 different http results. 2. Header-Checks 3. DNS- and NameServer - Checks A Info:: 15 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 8 Name Servers. A Info:: 15 Queries complete, 15 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. A Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns05.jpmorganchase.com (159.53.110.152), ns06.jpmorganchase.com (159.53.110.153), ns1.jpmorganchase.com (159.53.46.53), ns2.jpmorganchase.com (159.53.78.53) A Good (1 - 3.0):: An average of 1.9 queries per domain name server required to find all ip addresses of all name servers. A Info:: 8 different Name Servers found: ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com, ns1.p59.dynect.net, ns2.jpmorganchase.com, ns2.p59.dynect.net, ns3.p59.dynect.net, ns4.p59.dynect.net, 8 Name Servers included in Delegation: ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com, ns1.p59.dynect.net, ns2.jpmorganchase.com, ns2.p59.dynect.net, ns3.p59.dynect.net, ns4.p59.dynect.net, 8 Name Servers included in 1 Zone definitions: ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com, ns1.p59.dynect.net, ns2.jpmorganchase.com, ns2.p59.dynect.net, ns3.p59.dynect.net, ns4.p59.dynect.net, 1 Name Servers listed in SOA.Primary: ns1.jpmorganchase.com. A Good: Only one SOA.Primary Name Server found.: ns1.jpmorganchase.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1.jpmorganchase.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: ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com, ns1.p59.dynect.net, ns2.jpmorganchase.com, ns2.p59.dynect.net, ns3.p59.dynect.net, ns4.p59.dynect.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: 8 different Name Servers found A Good: Some Name Servers have IPv6 addresses: 2 Name Servers with IPv6 found (6 Name Servers without IPv6) A Good: Name servers with different Top Level Domains / Public Suffix List entries found: 8 Name Servers, 2 Top Level Domains: net, com A Good: Name Servers with different domain names found.: 2 different Domains found Warning: All Name Servers from the same Country / IP location.: 8 Name Servers, 1 Countries: US A Info: Ipv4-Subnet-list: 8 Name Servers, 3 different subnets (first Byte): 159., 204., 208., 3 different subnets (first two Bytes): 159.53., 204.13., 208.78., 7 different subnets (first three Bytes): 159.53.110., 159.53.46., 159.53.78., 204.13.250., 204.13.251., 208.78.70., 208.78.71. 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:0500:, 2 different subnets (first three blocks): 2001:0500:0090:, 2001:0500:0094:, 2 different subnets (first four blocks): 2001:0500:0090:0001:, 2001:0500:0094:0001: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 10 good Nameserver A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates A Good: Nameserver supports Echo Capitalization: 10 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 10 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 10 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 https://www.chase.com/digital/resources/oops.html 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://www.chase.com/ 159.53.42.11 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.chase.com/ 159.53.85.137 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.chase.com/digital/resources/oops.html 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.chase.com/ 159.53.42.11 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.chase.com/ 159.53.85.137 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.chase.com/digital/resources/oops.html 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.chase.com/ 159.53.42.11 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.chase.com/ 159.53.85.137 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.chase.com/digital/resources/oops.html Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.chase.com/ 159.53.42.11 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.: 4 script elements without defer/async. https://www.chase.com/ 159.53.85.137 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.: 4 script elements without defer/async. https://www.chase.com/digital/resources/oops.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.: 4 script elements without defer/async. Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 16 external CSS / JavaScript 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, 16 complete. 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: 422763 milliseconds, 422.763 seconds