| 1. General Results, most used to calculate the result |
| A | name "mail.pk-polimer.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: 2884 (complete: 239099)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: mail.pk-polimer.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: mail.pk-polimer.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://mail.pk-polimer.ru/owa/
| https://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
| Correct redirect https to https
|
| A | https://mail.pk-polimer.ru/ 78.36.205.190
| https://mail.pk-polimer.ru/owa/
| Correct redirect https to https
|
| A | https://78.36.205.190/owa/
| https://78.36.205.190/owa/auth/logon.aspx?url=https%3a%2f%2f78.36.205.190%2fowa%2f&reason=0
| Correct redirect https to https
|
| A | https://78.36.205.190/ 78.36.205.190
| https://78.36.205.190/owa/
| Correct redirect https to https
|
| 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: 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.
|
| B | https://mail.pk-polimer.ru/owa/
|
| Missing HSTS-Header
|
| B | https://mail.pk-polimer.ru/ 78.36.205.190
|
| Missing HSTS-Header
|
| B | https://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
|
| Missing HSTS-Header
|
| I | https://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| M | http://mail.pk-polimer.ru/ 78.36.205.190
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://mail.pk-polimer.ru/owa/
| https://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://mail.pk-polimer.ru/ 78.36.205.190
| https://mail.pk-polimer.ru/owa/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://78.36.205.190/owa/
| https://78.36.205.190/owa/auth/logon.aspx?url=https%3a%2f%2f78.36.205.190%2fowa%2f&reason=0
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://78.36.205.190/ 78.36.205.190
| https://78.36.205.190/owa/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://78.36.205.190/owa/auth/logon.aspx?url=https%3a%2f%2f78.36.205.190%2fowa%2f&reason=0
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | mail.pk-polimer.ru:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| O | mail.pk-polimer.ru / 78.36.205.190 / 25
|
| 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. 7 Cipher Suites without Forward Secrecy found
|
| O | mail.pk-polimer.ru / 78.36.205.190 / 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. 7 Cipher Suites without Forward Secrecy found
|
| 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 mail.pk-polimer.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.mail.pk-polimer.ru
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| A | mail.pk-polimer.ru
| 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.
|
| F | mail.pk-polimer.ru
| Content-Security-Policy
| Critical: Missing Header:
|
| F | mail.pk-polimer.ru
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | mail.pk-polimer.ru
| Referrer-Policy
| Critical: Missing Header:
|
| F | mail.pk-polimer.ru
| Permissions-Policy
| Critical: Missing Header:
|
| 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.reg.ru (176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, 194.58.117.17, 194.67.73.173, 194.67.73.174, 2a00:f940:4::47), ns2.reg.ru (176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, 194.58.117.18, 194.67.73.175, 194.67.73.176, 2a00:f940:5::190)
|
| 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.reg.ru, ns2.reg.ru, 2 Name Servers included in Delegation: ns1.reg.RU, ns2.reg.RU, 2 Name Servers included in 1 Zone definitions: ns1.reg.ru, ns2.reg.ru, 1 Name Servers listed in SOA.Primary: ns1.reg.ru.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.reg.ru.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.reg.ru.
|
| 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.reg.ru, ns2.reg.ru
|
| 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: 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: ru
|
| 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: reg.ru
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: RU
|
| A | Info: Ipv4-Subnet-list: 20 Name Servers, 2 different subnets (first Byte): 176., 194., 3 different subnets (first two Bytes): 176.99., 194.58., 194.67., 3 different subnets (first three Bytes): 176.99.13., 194.58.117., 194.67.73.
|
| 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): 2a00:, 1 different subnets (first two blocks): 2a00:f940:, 2 different subnets (first three blocks): 2a00:f940:0004:, 2a00:f940:0005:, 2 different subnets (first four blocks): 2a00:f940:0004:0000:, 2a00:f940:0005:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 11 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 11 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 11 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 11 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.reg.ru: 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.
|
| X | Fatal error: Nameservers with different SOA Serial Numbers
|
| 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://mail.pk-polimer.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 78.36.205.190
|
| 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.
|
| https://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://78.36.205.190/owa/auth/logon.aspx?url=https%3a%2f%2f78.36.205.190%2fowa%2f&reason=0
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
|
| 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://78.36.205.190/owa/auth/logon.aspx?url=https%3a%2f%2f78.36.205.190%2fowa%2f&reason=0
|
| 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://mail.pk-polimer.ru/owa/auth/logon.aspx?url=https%3a%2f%2fmail.pk-polimer.ru%2fowa%2f&reason=0
|
| 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://78.36.205.190/owa/auth/logon.aspx?url=https%3a%2f%2f78.36.205.190%2fowa%2f&reason=0
|
| 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.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 12 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, 12 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: Some img-elements have a valid alt-attribute.: 12 img-elements found, 2 img-elements with correct alt-attributes (defined, not an empty value).
|
| 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.: 10 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: 416216 milliseconds, 416.216 seconds
|