1. General Results, most used to calculate the result A name "bitrix.ininco.ru" is subdomain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 2123 (complete: 199710) A Good: All ip addresses are public addresses Warning: Only one ip address found: bitrix.ininco.ru 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: bitrix.ininco.ru 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://91.146.51.222/ 91.146.51.222 https://bitrix.ininco.ru/ 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://bitrix.ininco.ru/ 91.146.51.222 Missing HSTS-Header http://bitrix.ininco.ru/ 91.146.51.222 PHPSESSID=zkEUPxhDwoeP9HwY1Jmyy32FM4sVXqUM; 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://bitrix.ininco.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.146.51.222 PHPSESSID=6I73hKPrZTZCzGz3GoTXNde20bJfQeVH; 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. B https://bitrix.ininco.ru/ 91.146.51.222 PHPSESSID=gae41p8maSgkXwe3Issk7lD5LJarzjgQ; path=/; HttpOnly Cookie sent via https, but not marked as secure B https://91.146.51.222/ 91.146.51.222 PHPSESSID=2zcNVi0ZmKX9xwiIMG2StQ53GpnnAXza; path=/; HttpOnly Cookie sent via https, but not marked as secure B http://bitrix.ininco.ru/ 91.146.51.222 PHPSESSID=zkEUPxhDwoeP9HwY1Jmyy32FM4sVXqUM; 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://bitrix.ininco.ru/ 91.146.51.222 PHPSESSID=gae41p8maSgkXwe3Issk7lD5LJarzjgQ; 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://bitrix.ininco.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.146.51.222 PHPSESSID=6I73hKPrZTZCzGz3GoTXNde20bJfQeVH; 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://91.146.51.222/ 91.146.51.222 PHPSESSID=2zcNVi0ZmKX9xwiIMG2StQ53GpnnAXza; 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. 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://bitrix.ininco.ru/ 91.146.51.222 Error - Certificate isn't trusted, RemoteCertificateChainErrors N https://91.146.51.222/ 91.146.51.222 https://bitrix.ininco.ru/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors 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 bitrix.ininco.ru, 1 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.bitrix.ininco.ru 2. Header-Checks 3. DNS- and NameServer - Checks A Info:: 21 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 21 Queries complete, 20 with IPv6, 1 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. Bad (greater 8):: An average of 10.5 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: dns1.yandex.net, dns2.yandex.net, 2 Name Servers included in Delegation: dns1.yandex.net, dns2.yandex.net, 2 Name Servers included in 1 Zone definitions: dns1.yandex.net, dns2.yandex.net, 1 Name Servers listed in SOA.Primary: dns1.yandex.net. A Good: Only one SOA.Primary Name Server found.: dns1.yandex.net. A Good: SOA.Primary Name Server included in the delegation set.: dns1.yandex.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: dns1.yandex.net, dns2.yandex.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: yandex.net Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: RU A Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 213., 93., 2 different subnets (first two Bytes): 213.180., 93.158., 2 different subnets (first three Bytes): 213.180.204., 93.158.134. A Excellent: Every Name Server IPv4-address starts with an unique Byte. A Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a02:, 1 different subnets (first two blocks): 2a02:06b8:, 1 different subnets (first three blocks): 2a02:06b8:0000:, 2 different subnets (first four blocks): 2a02:06b8:0000:0000:, 2a02:06b8:0000:0001: A Good: Name Server IPv6 addresses from different subnets 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 Nameserver doesn't pass all EDNS-Checks: dns1.yandex.net: 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 http://bitrix.ininco.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.146.51.222 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://bitrix.ininco.ru/ 91.146.51.222 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://bitrix.ininco.ru/ 91.146.51.222 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://bitrix.ininco.ru/ 91.146.51.222 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.: 7 script elements without defer/async. A Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 13 external CSS / JavaScript files found A Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 13 external CSS / JavaScript files with long Cache-Control max-age found 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: 161640 milliseconds, 161.640 seconds