1. General Results, most used to calculate the result A name "vle.ase.md" is subdomain, public suffix is ".md", top-level-domain is ".md", top-level-domain-type is "country-code", Country is Moldova (the Republic of), tld-manager is "MoldData S.E.", num .md-domains preloaded: 38 (complete: 199710) A Good: All ip addresses are public addresses Warning: Only one ip address found: vle.ase.md has only one ip address. Warning: Only one ip address found: www.vle.ase.md 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: vle.ase.md 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.vle.ase.md has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A https://vle.ase.md/ 81.180.69.142 https://vle.ase.md/info/ Correct redirect https to https A https://www.vle.ase.md/ 81.180.69.142 https://www.vle.ase.md/info/ Correct redirect https to https A https://81.180.69.142/ 81.180.69.142 https://vle.ase.md/info/ Correct redirect https to https A Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None 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://vle.ase.md/ 81.180.69.142 Missing HSTS-Header B https://vle.ase.md/info/ Missing HSTS-Header B https://www.vle.ase.md/ 81.180.69.142 Missing HSTS-Header B https://www.vle.ase.md/info/ Missing HSTS-Header http://vle.ase.md/ 81.180.69.142 op_browser_state=dc5324c36908e682a829b03fab0054cb94e3a74903266642c427c492; Path=/; SameSite=lax 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://vle.ase.md/info/ op_browser_state=7432b2db798e3226ce3ad874beea2bcf913f219cca8c550a5a39e4c1; Path=/; SameSite=lax 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://vle.ase.md/info/ csrftoken=PqRameJkjm0EiKkFNIo59Zev2YthhgPQM6ChkTu6ITn5YGa45jpFrigYzw7H5QzG; expires=Wed, 04 Oct 2023 07:15:19 GMT; Max-Age=31449600; Path=/; SameSite=Lax 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://www.vle.ase.md/ 81.180.69.142 op_browser_state=dddddef35bd65ba348a59426adbcdb0d4d24028c6e7787466e712809; Path=/; SameSite=lax 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://www.vle.ase.md/info/ op_browser_state=2d70d490e64c59abe92462de9e9a5fb6a103d288ba4deb705467802e; Path=/; SameSite=lax 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://www.vle.ase.md/info/ csrftoken=P7kgwZurAOq6Nza2ttQBr6MHuE14Tz1G3NsyLewEDfZSYFeOcDiYvMlebMH3vbFs; expires=Wed, 04 Oct 2023 07:15:19 GMT; Max-Age=31449600; Path=/; SameSite=Lax 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://vle.ase.md/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 81.180.69.142 op_browser_state=63c2f7c1295b1bdf1071603154dcbf20d4f001dde843bd992e0814ad; Path=/; SameSite=lax 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://www.vle.ase.md/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 81.180.69.142 op_browser_state=fa6d5bcc994b8505c9d48dec4599929f2deb162dd081d2ddc977a9b1; Path=/; SameSite=lax 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://vle.ase.md/ 81.180.69.142 op_browser_state=dddddef35bd65ba348a59426adbcdb0d4d24028c6e7787466e712809; Path=/; SameSite=lax Cookie sent via https, but not marked as secure B https://vle.ase.md/info/ op_browser_state=4d20c6613a286e307845bfe44fd41fae952a04b24e9a4b5d2111f0c8; Path=/; SameSite=lax Cookie sent via https, but not marked as secure B https://vle.ase.md/info/ csrftoken=EzkACilal52HggQe8eaphE5u4aaNUdvQx7NsiAPCXGIERVemMG14XGOTsXHG13pG; expires=Wed, 04 Oct 2023 07:15:19 GMT; Max-Age=31449600; Path=/; SameSite=Lax Cookie sent via https, but not marked as secure B https://www.vle.ase.md/ 81.180.69.142 op_browser_state=418a8f766bb8dff03ed233ff247e674f634d207c338586bc7fb2af47; Path=/; SameSite=lax Cookie sent via https, but not marked as secure B https://www.vle.ase.md/info/ op_browser_state=dddddef35bd65ba348a59426adbcdb0d4d24028c6e7787466e712809; Path=/; SameSite=lax Cookie sent via https, but not marked as secure B https://www.vle.ase.md/info/ csrftoken=upMvMfwnJxEGT0am8HskGfXmWSUYQd4K7wf0h6d8vLodWBUcWIaInzJzDBoCoCJs; expires=Wed, 04 Oct 2023 07:15:23 GMT; Max-Age=31449600; Path=/; SameSite=Lax Cookie sent via https, but not marked as secure B https://81.180.69.142/ 81.180.69.142 op_browser_state=75714b8cdae245ac3152da6ed18ab93cd7823a26bbb051b3f03cb2cd; Path=/; SameSite=lax Cookie sent via https, but not marked as secure 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. N https://81.180.69.142/ 81.180.69.142 https://vle.ase.md/info/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch 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 vle.ase.md, 1 ip addresses, 1 different http results. 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 www.vle.ase.md, 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.vle.ase.md 2. Header-Checks 3. DNS- and NameServer - Checks A Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers. A Info:: 7 Queries complete, 3 with IPv6, 4 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. A Info:: 3 different Name Servers found: ns.ase.md, ns.vle.ase.md, vle.ase.md, 2 Name Servers included in Delegation: ns.vle.ase.md, vle.ase.md, 3 Name Servers included in 2 Zone definitions: ns.ase.md, ns.vle.ase.md, vle.ase.md, 1 Name Servers listed in SOA.Primary: ns.vle.ase.md. A Good: Only one SOA.Primary Name Server found.: ns.vle.ase.md. A Good: SOA.Primary Name Server included in the delegation set.: ns.vle.ase.md. 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.: ns.vle.ase.md (81.180.69.142): Delegation: ns.vle.ase.md, vle.ase.md, Zone: ns.ase.md, ns.vle.ase.md, vle.ase.md. Name Servers defined in Zone, missing in Delegation: ns.ase.md. 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.: vle.ase.md (81.180.69.142): Delegation: ns.vle.ase.md, vle.ase.md, Zone: ns.ase.md, ns.vle.ase.md, vle.ase.md. Name Servers defined in Zone, missing in Delegation: ns.ase.md. A Good: All Name Server Domain Names have a Public Suffix. Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1 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: md 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: ase.md Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: MD A Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 81., 1 different subnets (first two Bytes): 81.180., 1 different subnets (first three Bytes): 81.180.69. 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.: X Fatal: Only one Name Server IPv4 address found. 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 Info: Nameserver mit different domain names found. May be a problem with DNS-Updates 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: 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. A Good: Every https result with status 200 supports GZip. https://vle.ase.md/info/ 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.vle.ase.md/info/ 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://vle.ase.md/info/ 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://www.vle.ase.md/info/ 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 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: 188543 milliseconds, 188.543 seconds