1. General Results, most used to calculate the result A name "api.botmaster.cf" is subdomain, public suffix is ".cf", top-level-domain is ".cf", top-level-domain-type is "country-code", Country is Central African Republic (the), tld-manager is "Societe Centrafricaine de Telecommunications (SOCATEL)", num .cf-domains preloaded: 1586 (complete: 151507) A good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: api.botmaster.cf has 4 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: api.botmaster.cf has 2 ipv4, 2 ipv6 addresses 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 good - only one version with Http-Status 200 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (12 urls) http://api.botmaster.cf/ 104.21.49.206 Url with incomplete Content-Type - header - missing charset http://api.botmaster.cf/ 172.67.192.136 Url with incomplete Content-Type - header - missing charset http://api.botmaster.cf/ 2606:4700:3034::ac43:c088 Url with incomplete Content-Type - header - missing charset http://api.botmaster.cf/ 2606:4700:3035::6815:31ce Url with incomplete Content-Type - header - missing charset https://api.botmaster.cf/ 104.21.49.206 Url with incomplete Content-Type - header - missing charset https://api.botmaster.cf/ 172.67.192.136 Url with incomplete Content-Type - header - missing charset https://api.botmaster.cf/ 2606:4700:3034::ac43:c088 Url with incomplete Content-Type - header - missing charset https://api.botmaster.cf/ 2606:4700:3035::6815:31ce Url with incomplete Content-Type - header - missing charset http://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.49.206 Url with incomplete Content-Type - header - missing charset http://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.192.136 Url with incomplete Content-Type - header - missing charset http://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3034::ac43:c088 Url with incomplete Content-Type - header - missing charset http://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3035::6815:31ce Url with incomplete Content-Type - header - missing charset B https://api.botmaster.cf/ 104.21.49.206 Missing HSTS-Header B https://api.botmaster.cf/ 172.67.192.136 Missing HSTS-Header B https://api.botmaster.cf/ 2606:4700:3034::ac43:c088 Missing HSTS-Header B https://api.botmaster.cf/ 2606:4700:3035::6815:31ce Missing HSTS-Header http://api.botmaster.cf/ 104.21.49.206 __cfduid=d1892c23056b5a0b264d86ce6774065071617828978; expires=Fri, 07-May-21 20:56:18 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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://api.botmaster.cf/ 172.67.192.136 __cfduid=d6e1bdb6772fdaed505bdbeb09f37c5ba1617828978; expires=Fri, 07-May-21 20:56:18 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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://api.botmaster.cf/ 2606:4700:3034::ac43:c088 __cfduid=d8e9838813e6e07c55b1aeeb26bd0312f1617828978; expires=Fri, 07-May-21 20:56:18 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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://api.botmaster.cf/ 2606:4700:3035::6815:31ce __cfduid=dffe99163d97a1f5c4de83e553f4620bc1617828979; expires=Fri, 07-May-21 20:56:19 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.49.206 __cfduid=d4c76a1ac9c7465c633342208a32e6f421617828991; expires=Fri, 07-May-21 20:56:31 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.192.136 __cfduid=d7eab8c1ac58b90b37907ba0ce68636401617828991; expires=Fri, 07-May-21 20:56:31 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3034::ac43:c088 __cfduid=d82f61e2e243a528bfc18401bb164e8aa1617828991; expires=Fri, 07-May-21 20:56:31 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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://api.botmaster.cf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3035::6815:31ce __cfduid=dbc7562384ad08d2fdde891433310e5291617828991; expires=Fri, 07-May-21 20:56:31 GMT; path=/; domain=.botmaster.cf; HttpOnly; 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. Cloudflare __cfduid Cookie via http found. Activate "Always Use HTTPS", then these cookies only sent via https. Check https://support.cloudflare.com/hc/en-us/articles/200170156-Understanding-the-Cloudflare-Cookies B https://api.botmaster.cf/ 104.21.49.206 __cfduid=d75577c6a6ea28a6ffd8cf848e904e6b31617828979; expires=Fri, 07-May-21 20:56:19 GMT; path=/; domain=.botmaster.cf; HttpOnly; SameSite=Lax Cookie sent via https, but not marked as secure B https://api.botmaster.cf/ 172.67.192.136 __cfduid=de7d3ced84c404911467e604699c41b531617828982; expires=Fri, 07-May-21 20:56:22 GMT; path=/; domain=.botmaster.cf; HttpOnly; SameSite=Lax Cookie sent via https, but not marked as secure B https://api.botmaster.cf/ 2606:4700:3034::ac43:c088 __cfduid=d4484d36833825b3db321f48f3ad80a6a1617828985; expires=Fri, 07-May-21 20:56:25 GMT; path=/; domain=.botmaster.cf; HttpOnly; SameSite=Lax Cookie sent via https, but not marked as secure B https://api.botmaster.cf/ 2606:4700:3035::6815:31ce __cfduid=dc8884682957248aca6343ee70f797cab1617828988; expires=Fri, 07-May-21 20:56:28 GMT; path=/; domain=.botmaster.cf; HttpOnly; SameSite=Lax Cookie sent via https, but not marked as secure H fatal error: No https - result with http-status 200, no encryption 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. M https://api.botmaster.cf/ 104.21.49.206 Misconfiguration - main pages should never send http status 400 - 499 M https://api.botmaster.cf/ 172.67.192.136 Misconfiguration - main pages should never send http status 400 - 499 M https://api.botmaster.cf/ 2606:4700:3034::ac43:c088 Misconfiguration - main pages should never send http status 400 - 499 M https://api.botmaster.cf/ 2606:4700:3035::6815:31ce Misconfiguration - main pages should never send http status 400 - 499 P https://104.21.49.206/ 104.21.49.206 Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2 P https://172.67.192.136/ 172.67.192.136 Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2 P https://[2606:4700:3034:0000:0000:0000:ac43:c088]/ 2606:4700:3034::ac43:c088 Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2 P https://[2606:4700:3035:0000:0000:0000:6815:31ce]/ 2606:4700:3035::6815:31ce Error creating a TLS-Connection: TLSv1.3 found, but no connection via TLSv1.2 possible. Please activate TLSv1.2 A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain api.botmaster.cf, 4 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 api.botmaster.cf, 4 ip addresses. 2. DNS- and NameServer - Checks A Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: davina.ns.cloudflare.com, leonidas.ns.cloudflare.com, 2 Name Servers included in Delegation: davina.ns.cloudflare.com, leonidas.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: davina.ns.cloudflare.com, leonidas.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: davina.ns.cloudflare.com. A Good: Only one SOA.Primary Name Server found.: davina.ns.cloudflare.com. A Good: SOA.Primary Name Server included in the delegation set.: davina.ns.cloudflare.com. 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: davina.ns.cloudflare.com, leonidas.ns.cloudflare.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: 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: cloudflare.com A Good: Name servers with different Country locations found: 2 Name Servers, 4 Countries: CA, CR, GB, US A Info: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 108., 162., 172., 3 different subnets (first two Bytes): 108.162., 162.159., 172.64., 6 different subnets (first three Bytes): 108.162.194., 108.162.195., 162.159.38., 162.159.44., 172.64.34., 172.64.35. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 6 good Nameserver A Good: Nameserver supports Echo Capitalization: 6 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver Nameserver doesn't pass all EDNS-Checks: davina.ns.cloudflare.com: 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. 3. 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: 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: 235814 milliseconds, 235.814 seconds