| 1. General Results, most used to calculate the result |
| A | name "efforce.xyz" is domain, public suffix is ".xyz", top-level-domain is ".xyz", top-level-domain-type is "generic", tld-manager is "XYZ.COM LLC", num .xyz-domains preloaded: 947 (complete: 131120)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: efforce.xyz has only one ip address.
|
| Warning: Only one ip address found: www.efforce.xyz 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: efforce.xyz 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.efforce.xyz has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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)
|
| http://efforce.xyz/ 165.22.4.106
| XSRF-TOKEN=eyJpdiI6InVTWXk3eUVIMG5iU2w1cUhqak1lK0E9PSIsInZhbHVlIjoibFFweUlmbzJyeHVpZXljU3BaVy9pc21QUkFZQzVIUkFza2pzT3JnVC9PbmZ3Z0h5RHVKcXpHQjBON2dOTlJmdmZPZGNGRUNvWFl5ZDFuaFJ0TGswR1NvU05rQXNFZmp1ell6dHNoQkVCdjZqeHZBT2tBY3BvSjZCZWNuanBnUC8iLCJtYWMiOiI3ZGUyZTFmMjhjOWQ0ZDMzMTdlNDhlY2M0ZGFhM2ViYTQwOGVhMDRlNmRlMjI0MzVkYTcxNmY2NjMwYjBjMzA4In0%3D; expires=Mon, 14-Dec-2020 03:10:06 GMT; Max-Age=7200; 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://efforce.xyz/ 165.22.4.106
| efforce_session=eyJpdiI6IjUyZHhqdnJvUytDaUgwR1A2Vm52cXc9PSIsInZhbHVlIjoiVHZXUTZwWUZNVERaUDdDZk8yTnovaXNZeVNyUDNQNlBldHV1anduRFRhaUJQTytPSU9QTDdDMFU1UGZBc2RNbXhUWVdQZzNXRVk2QWxXdWZlaWRZaTJiaFh0a2RJVnMyQVZBWUJRZm8wV0JVWW8zLy9yNjVrYTZDVjlTb3dMTVoiLCJtYWMiOiI5Y2FhOGY4YjQwZWE0ODlkYWFlNGQzMGIwNGIwYTY3MDA5ODM3ZmEzMjIxMzljN2ZiYzdmM2Y3ZjM2YWZkNDFmIn0%3D; expires=Mon, 14-Dec-2020 03:10:06 GMT; Max-Age=7200; path=/; 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://www.efforce.xyz/ 165.22.4.106
| XSRF-TOKEN=eyJpdiI6IkNJWlZzNnlrelBFVm9SbUIvNkxNN3c9PSIsInZhbHVlIjoiNjU3Ri82RThFajJ0VzBpNTVoRFlUdGRCRzRWT2NlYjNwRERLTUFNc0xlaG5wZWxtUDUrYWhDUldWdUdsL2NJekgyeDR1RlRwT1R1NmNlVWJQQ29FcjVsdDJvMTQrUlJwd0grUXVWOHlVamVtN1piT1JLR3BRKzlESjdBbEZtSnoiLCJtYWMiOiJkODdmMDE1ZmM3NzA5NWFmYzg4YTFmOGNiMmJiOGU5YzAzMTVmODIzMWM1ZjNkMzY5ODlkMWZmMGU3YjMyYmU1In0%3D; expires=Mon, 14-Dec-2020 03:10:06 GMT; Max-Age=7200; 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.efforce.xyz/ 165.22.4.106
| efforce_session=eyJpdiI6ImtSdlhHK0VNK1Bpb2RIcGVhU2h5RlE9PSIsInZhbHVlIjoiQTdoNCs0MlNqT1VCcVBXMjdwU3hTZXhMRXRnc3JBN0dSNStUUm5QVjAyTTdqZGMvclVOays1VzJTdkZ6QWtHeHV3L001UDl1cUFVRjM1Tkw2WTN4bE5TM2U3ZVo3TVNKdEl0dnlXSDFXUGltTDdwcWs0bHdkQjQ0RFludyt5MnciLCJtYWMiOiJlMTc5OTg4MTdlMzkwY2ZjOTZhZTljYzU1MjE1NDI3MTY3ZTg3OWVkNTBmZTcwMGZhN2YwOWM2NWEyOTZjMzI1In0%3D; expires=Mon, 14-Dec-2020 03:10:06 GMT; Max-Age=7200; path=/; 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.
|
| 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: 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.
|
| V | https://efforce.xyz/ 165.22.4.106
|
| Connect failure - perhaps firewall
|
| V | https://www.efforce.xyz/ 165.22.4.106
|
| Connect failure - perhaps firewall
|
| V | https://165.22.4.106/ 165.22.4.106
|
| Connect failure - perhaps firewall
|
| 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 efforce.xyz, 1 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 www.efforce.xyz, 1 ip addresses.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in Delegation: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in 1 Zone definitions: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 1 Name Servers listed in SOA.Primary: ns1.digitalocean.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.digitalocean.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.digitalocean.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: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.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: 3 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 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: digitalocean.com
|
| A | Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: CA, US
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 173., 198., 2 different subnets (first two Bytes): 173.245., 198.41., 3 different subnets (first three Bytes): 173.245.58., 173.245.59., 198.41.222.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
| 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: ns0.centralnic.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 |
| 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 CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 2 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, 2 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete.
|
| 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: 53227 milliseconds, 53.227 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)