| 1. General Results, most used to calculate the result |
| A | name "spetspribor-nt.ru" is domain, public suffix is "ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| A | Good: HSTS has preload directive
|
| Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
|
| 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):1 complete Content-Type - header (3 urls)
|
| http://spetspribor-nt.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.146.47.206
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.spetspribor-nt.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.146.47.206
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://spetspribor-nt.ru/ 82.146.47.206
| https://spetspribor-nt.ru/
| Correct redirect http - https with the same domain name
|
| A | http://www.spetspribor-nt.ru/ 82.146.47.206
| https://www.spetspribor-nt.ru/
| Correct redirect http - https with the same domain name
|
| X | Fatal error: Nameserver doesn't support TCP connection: firstvds.ru: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 82.202.175.68:53
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
| 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.firstvds.ru,ns2.firstvds.ru
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: firstvds.ru
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| X | Nameserver Timeout checking EDNS512: firstvds.ru
|
| 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: firstvds.ru: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| A | http://spetspribor-nt.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.146.47.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.spetspribor-nt.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.146.47.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://spetspribor-nt.ru/ 82.146.47.206
|
| 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://spetspribor-nt.ru/ 82.146.47.206
|
| 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://spetspribor-nt.ru/ 82.146.47.206
|
| 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.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 10 external CSS / JavaScript files found
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 9 with Cache-Control long enough, 10 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 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), 5 with Cache-Control long enough, 6 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 1 img-elements 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: 118306 milliseconds, 118.306 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)