| 1. General Results, most used to calculate the result |
| A | name "pinakis.co.in" is domain, public suffix is ".co.in", top-level-domain is ".in", top-level-domain-type is "country-code", Country is India, tld-manager is "National Internet Exchange of India", num .in-domains preloaded: 541 (complete: 142558)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: pinakis.co.in has only one ip address.
|
| Warning: Only one ip address found: www.pinakis.co.in 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: pinakis.co.in 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.pinakis.co.in has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (6 urls)
|
| http://pinakis.co.in/ 185.27.134.117
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.pinakis.co.in/ 185.27.134.117
|
| Url with incomplete Content-Type - header - missing charset
|
| https://pinakis.co.in/ 185.27.134.117
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.pinakis.co.in/ 185.27.134.117
|
| Url with incomplete Content-Type - header - missing charset
|
| http://pinakis.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.117
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.pinakis.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.117
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://pinakis.co.in/ 185.27.134.117
|
| Missing HSTS-Header
|
| B | https://www.pinakis.co.in/ 185.27.134.117
|
| 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.
|
| 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.
|
| J | https://pinakis.co.in/ 185.27.134.117
|
| Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file.
|
| J | https://www.pinakis.co.in/ 185.27.134.117
|
| Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file.
|
| J | http://pinakis.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.117
|
| Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file.
|
| J | http://www.pinakis.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.117
|
| Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file.
|
| N | https://pinakis.co.in/ 185.27.134.117
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.pinakis.co.in/ 185.27.134.117
|
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| P | https://185.27.134.117/ 185.27.134.117
|
| Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain pinakis.co.in, 1 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.pinakis.co.in, 1 ip addresses.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 2 Queries complete, 2 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.ns1.epizy.com (185.27.134.7), ns2.epizy.com (37.187.64.39)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.epizy.com, ns2.epizy.com, 2 Name Servers included in Delegation: ns1.epizy.com, ns2.epizy.com, 1 Name Servers included in 1 Zone definitions: ns1.epizy.com, 1 Name Servers listed in SOA.Primary: ns1.epizy.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.epizy.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.epizy.com.
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.epizy.com (185.27.134.7): Delegation: ns1.epizy.com, ns2.epizy.com, Zone: ns1.epizy.com. Name Servers defined in Delegation, missing in Zone: ns2.epizy.com.
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.epizy.com (37.187.64.39): Delegation: ns1.epizy.com, ns2.epizy.com, Zone: ns1.epizy.com. Name Servers defined in Delegation, missing in Zone: ns2.epizy.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: epizy.com
|
| A | Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: FR, GB
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 185., 37., 2 different subnets (first two Bytes): 185.27., 37.187., 2 different subnets (first three Bytes): 185.27.134., 37.187.64.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| 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): 1 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.epizy.com: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (internaldns.byetcluster.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.epizy.com / 185.27.134.7: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (internaldns.byetcluster.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.neustar.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.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.neustar.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 |
| https://pinakis.co.in/ 185.27.134.117
|
| 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.pinakis.co.in/ 185.27.134.117
|
| 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://pinakis.co.in/ 185.27.134.117
|
| 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.pinakis.co.in/ 185.27.134.117
|
| 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://pinakis.co.in/ 185.27.134.117
|
| 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.: 1 script elements without defer/async.
|
| https://www.pinakis.co.in/ 185.27.134.117
|
| 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.: 1 script elements without defer/async.
|
| http://pinakis.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.117
|
| 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.: 1 script elements without defer/async.
|
| http://www.pinakis.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.117
|
| 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.: 1 script elements without defer/async.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 4 external CSS / JavaScript files without GZip found - 0 with GZip, 4 complete
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 4 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, 4 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: 68687 milliseconds, 68.687 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)