1. General Results, most used to calculate the result A name "msfa.progenerp.com" is subdomain, 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: 89449 (complete: 231048) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: msfa.progenerp.com has 2 different ip addresses (authoritative). 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: msfa.progenerp.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem A https://msfa.progenerp.com/ 103.51.26.94 https://msfa.progenerp.com/sfa/app_login_en/ Correct redirect https to https A https://msfa.progenerp.com/ 103.143.8.22 https://msfa.progenerp.com/sfa/app_login_en/ Correct redirect https to https A https://103.51.26.94/ 103.51.26.94 https://msfa.progenerp.com/sfa/app_login_en/ Correct redirect https to https A https://103.143.8.22/ 103.143.8.22 https://msfa.progenerp.com/sfa/app_login_en/ Correct redirect https to https A Good: one preferred version: non-www is preferred 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) B https://msfa.progenerp.com/ 103.51.26.94 Missing HSTS-Header B https://msfa.progenerp.com/ 103.143.8.22 Missing HSTS-Header B https://msfa.progenerp.com/sfa/app_login_en/ Missing HSTS-Header http://msfa.progenerp.com/sfa/app_login_en/ PHPSESSID=fgigh1lncvv75hdjb9r8bsds79; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://msfa.progenerp.com/sfa/app_login_en/ sc_actual_lang_SFA1=en_us; path=/ Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. B https://msfa.progenerp.com/sfa/app_login_en/ PHPSESSID=cebnhuubd900uacbkqpfp28cn8; path=/; HttpOnly Cookie sent via https, but not marked as secure B https://msfa.progenerp.com/sfa/app_login_en/ sc_actual_lang_SFA1=en_us; path=/ Cookie sent via https, but not marked as secure B http://msfa.progenerp.com/sfa/app_login_en/ PHPSESSID=fgigh1lncvv75hdjb9r8bsds79; path=/; HttpOnly 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 http://msfa.progenerp.com/sfa/app_login_en/ sc_actual_lang_SFA1=en_us; 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://msfa.progenerp.com/sfa/app_login_en/ PHPSESSID=cebnhuubd900uacbkqpfp28cn8; path=/; HttpOnly 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://msfa.progenerp.com/sfa/app_login_en/ sc_actual_lang_SFA1=en_us; 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. D http://msfa.progenerp.com/ 103.51.26.94 http://msfa.progenerp.com/sfa/app_login_en/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. D http://msfa.progenerp.com/ 103.143.8.22 http://msfa.progenerp.com/sfa/app_login_en/ Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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. H Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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. N https://103.51.26.94/ 103.51.26.94 https://msfa.progenerp.com/sfa/app_login_en/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://103.143.8.22/ 103.143.8.22 https://msfa.progenerp.com/sfa/app_login_en/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch O msfa.progenerp.com / 103.51.26.94 / 443 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 9 Cipher Suites without Forward Secrecy found O msfa.progenerp.com / 103.143.8.22 / 443 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 9 Cipher Suites without Forward Secrecy found 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 msfa.progenerp.com, 2 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 msfa.progenerp.com, 2 ip addresses, 1 different http results. B No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.msfa.progenerp.com 2. Header-Checks A msfa.progenerp.com X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A X-Xss-Protection Ok: Header without syntax errors found: 1; mode=block B Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block F msfa.progenerp.com Content-Security-Policy Critical: Missing Header: F msfa.progenerp.com X-Content-Type-Options Critical: Missing Header: F msfa.progenerp.com Referrer-Policy Critical: Missing Header: F msfa.progenerp.com Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 14 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 14 Queries complete, 14 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 7.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: cns1.hostgator.in, cns2.hostgator.in, 2 Name Servers included in Delegation: cns1.hostgator.in, cns2.hostgator.in, 2 Name Servers included in 1 Zone definitions: cns1.hostgator.in, cns2.hostgator.in, 1 Name Servers listed in SOA.Primary: cns1.hostgator.in. A Good: Only one SOA.Primary Name Server found.: cns1.hostgator.in. A Good: SOA.Primary Name Server included in the delegation set.: cns1.hostgator.in. 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: cns1.hostgator.in, cns2.hostgator.in 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: in 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: hostgator.in Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US A Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 108., 1 different subnets (first two Bytes): 108.179., 1 different subnets (first three Bytes): 108.179.246. X Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.: A Good: Nameserver supports TCP connections: 1 good Nameserver A Good: Nameserver supports Echo Capitalization: 1 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver Nameserver doesn't pass all EDNS-Checks: cns1.hostgator.in: 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. 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. https://msfa.progenerp.com/sfa/app_login_en/ Warning: https result with status 200 and size greater then 1024 Bytes without GZip found. Add GZip support so the html content is compressed. https://msfa.progenerp.com/sfa/app_login_en/ 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://msfa.progenerp.com/sfa/app_login_en/ 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://msfa.progenerp.com/sfa/app_login_en/ 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://msfa.progenerp.com/sfa/app_login_en/ 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. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 15 external CSS / JavaScript files without GZip found - 0 with GZip, 15 complete A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 2 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. 14 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), 1 with Cache-Control long enough, 15 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 5 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, 5 complete. A Good: Some checked attribute values are enclosed in quotation marks (" or ').: 35 Html-Elements checked, 34 without problems. I Wrong: Attribute values found, not enclosed in quotation marks (" or ').: 1 Html-Elements with attributes and missing enclosed quotation marks found. 1 wrong attributes. 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.: 5 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 A Duration: 536617 milliseconds, 536.617 seconds