1. General Results, most used to calculate the result A name "how.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 89449 (complete: 231048) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: how.com has 12 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.how.com has 12 different ip addresses (authoritative). 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: how.com 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.how.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout 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. A Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (56 urls) http://how.com/ 45.33.2.79 Url with incomplete Content-Type - header - missing charset http://how.com/ 45.33.18.44 Url with incomplete Content-Type - header - missing charset http://how.com/ 45.33.20.235 Url with incomplete Content-Type - header - missing charset http://how.com/ 45.33.23.183 Url with incomplete Content-Type - header - missing charset http://how.com/ 45.33.30.197 Url with incomplete Content-Type - header - missing charset http://how.com/ 45.56.79.23 Url with incomplete Content-Type - header - missing charset http://how.com/ 45.79.19.196 Url with incomplete Content-Type - header - missing charset http://how.com/ 72.14.178.174 Url with incomplete Content-Type - header - missing charset http://how.com/ 72.14.185.43 Url with incomplete Content-Type - header - missing charset http://how.com/ 96.126.123.244 Url with incomplete Content-Type - header - missing charset http://how.com/ 173.255.194.134 Url with incomplete Content-Type - header - missing charset http://how.com/ 198.58.118.167 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 45.33.2.79 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 45.33.18.44 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 45.33.20.235 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 45.33.23.183 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 45.33.30.197 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 45.56.79.23 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 45.79.19.196 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 72.14.178.174 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 72.14.185.43 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 96.126.123.244 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 173.255.194.134 Url with incomplete Content-Type - header - missing charset http://www.how.com/ 198.58.118.167 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.2.79 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.18.44 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.20.235 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.23.183 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.30.197 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.56.79.23 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.79.19.196 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 72.14.178.174 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 72.14.185.43 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 96.126.123.244 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 173.255.194.134 Url with incomplete Content-Type - header - missing charset http://how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.58.118.167 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.2.79 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.18.44 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.20.235 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.23.183 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.33.30.197 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.56.79.23 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.79.19.196 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 72.14.178.174 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 72.14.185.43 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 96.126.123.244 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 173.255.194.134 Url with incomplete Content-Type - header - missing charset http://www.how.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.58.118.167 Url with incomplete Content-Type - header - missing charset http://173.255.194.134/ Url with incomplete Content-Type - header - missing charset http://198.58.118.167/ Url with incomplete Content-Type - header - missing charset http://45.33.18.44/ Url with incomplete Content-Type - header - missing charset http://45.33.2.79/ Url with incomplete Content-Type - header - missing charset http://45.33.20.235/ Url with incomplete Content-Type - header - missing charset http://45.33.23.183/ Url with incomplete Content-Type - header - missing charset http://45.33.30.197/ Url with incomplete Content-Type - header - missing charset http://45.56.79.23/ Url with incomplete Content-Type - header - missing charset B https://how.com/ 45.33.2.79 Missing HSTS-Header B https://how.com/ 45.33.18.44 Missing HSTS-Header B https://how.com/ 45.33.20.235 Missing HSTS-Header B https://how.com/ 45.33.23.183 Missing HSTS-Header B https://how.com/ 45.33.30.197 Missing HSTS-Header B https://how.com/ 45.56.79.23 Missing HSTS-Header B https://how.com/ 45.79.19.196 Missing HSTS-Header B https://how.com/ 72.14.178.174 Missing HSTS-Header B https://how.com/ 72.14.185.43 Missing HSTS-Header B https://how.com/ 96.126.123.244 Missing HSTS-Header B https://how.com/ 173.255.194.134 Missing HSTS-Header B https://how.com/ 198.58.118.167 Missing HSTS-Header B https://www.how.com/ 45.33.2.79 Missing HSTS-Header B https://www.how.com/ 45.33.18.44 Missing HSTS-Header B https://www.how.com/ 45.33.20.235 Missing HSTS-Header B https://www.how.com/ 45.33.23.183 Missing HSTS-Header B https://www.how.com/ 45.33.30.197 Missing HSTS-Header B https://www.how.com/ 45.56.79.23 Missing HSTS-Header B https://www.how.com/ 45.79.19.196 Missing HSTS-Header B https://www.how.com/ 72.14.178.174 Missing HSTS-Header B https://www.how.com/ 72.14.185.43 Missing HSTS-Header B https://www.how.com/ 96.126.123.244 Missing HSTS-Header B https://www.how.com/ 173.255.194.134 Missing HSTS-Header B https://www.how.com/ 198.58.118.167 Missing HSTS-Header B https://how.com/ 45.33.2.79 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 45.33.18.44 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 45.33.20.235 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 45.33.23.183 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 45.33.30.197 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 45.56.79.23 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 45.79.19.196 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 72.14.178.174 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 72.14.185.43 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 96.126.123.244 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 173.255.194.134 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 198.58.118.167 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 45.33.2.79 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 45.33.18.44 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 45.33.20.235 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 45.33.23.183 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 45.33.30.197 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 45.56.79.23 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 45.79.19.196 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 72.14.178.174 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 72.14.185.43 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 96.126.123.244 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 173.255.194.134 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://www.how.com/ 198.58.118.167 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://45.33.2.79/ 45.33.2.79 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://45.33.18.44/ 45.33.18.44 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://45.33.20.235/ 45.33.20.235 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://45.33.23.183/ 45.33.23.183 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://45.33.30.197/ 45.33.30.197 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://45.56.79.23/ 45.56.79.23 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://45.79.19.196/ 45.79.19.196 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://72.14.178.174/ 72.14.178.174 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://72.14.185.43/ 72.14.185.43 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://96.126.123.244/ 96.126.123.244 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://173.255.194.134/ 173.255.194.134 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://198.58.118.167/ 198.58.118.167 mtmssl=1; path=/; Cookie sent via https, but not marked as secure B https://how.com/ 45.33.2.79 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 45.33.18.44 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 45.33.20.235 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 45.33.23.183 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 45.33.30.197 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 45.56.79.23 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 45.79.19.196 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 72.14.178.174 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 72.14.185.43 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 96.126.123.244 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 173.255.194.134 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://how.com/ 198.58.118.167 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 45.33.2.79 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 45.33.18.44 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 45.33.20.235 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 45.33.23.183 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 45.33.30.197 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 45.56.79.23 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 45.79.19.196 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 72.14.178.174 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 72.14.185.43 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 96.126.123.244 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 173.255.194.134 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://www.how.com/ 198.58.118.167 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://45.33.2.79/ 45.33.2.79 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://45.33.18.44/ 45.33.18.44 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://45.33.20.235/ 45.33.20.235 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://45.33.23.183/ 45.33.23.183 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://45.33.30.197/ 45.33.30.197 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://45.56.79.23/ 45.56.79.23 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://45.79.19.196/ 45.79.19.196 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://72.14.178.174/ 72.14.178.174 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://72.14.185.43/ 72.14.185.43 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://96.126.123.244/ 96.126.123.244 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://173.255.194.134/ 173.255.194.134 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B https://198.58.118.167/ 198.58.118.167 mtmssl=1; path=/; Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. F https://how.com/ 45.33.2.79 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 45.33.18.44 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 45.33.20.235 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 45.33.23.183 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 45.33.30.197 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 45.56.79.23 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 45.79.19.196 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 72.14.178.174 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 72.14.185.43 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 96.126.123.244 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 173.255.194.134 http://how.com/ Wrong redirect https - http - never redirect https to http F https://how.com/ 198.58.118.167 http://how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 45.33.2.79 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 45.33.18.44 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 45.33.20.235 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 45.33.23.183 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 45.33.30.197 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 45.56.79.23 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 45.79.19.196 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 72.14.178.174 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 72.14.185.43 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 96.126.123.244 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 173.255.194.134 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://www.how.com/ 198.58.118.167 http://www.how.com/ Wrong redirect https - http - never redirect https to http F https://45.33.2.79/ 45.33.2.79 http://45.33.2.79/ Wrong redirect https - http - never redirect https to http F https://45.33.18.44/ 45.33.18.44 http://45.33.18.44/ Wrong redirect https - http - never redirect https to http F https://45.33.20.235/ 45.33.20.235 http://45.33.20.235/ Wrong redirect https - http - never redirect https to http F https://45.33.23.183/ 45.33.23.183 http://45.33.23.183/ Wrong redirect https - http - never redirect https to http F https://45.33.30.197/ 45.33.30.197 http://45.33.30.197/ Wrong redirect https - http - never redirect https to http F https://45.56.79.23/ 45.56.79.23 http://45.56.79.23/ Wrong redirect https - http - never redirect https to http F https://173.255.194.134/ 173.255.194.134 http://173.255.194.134/ Wrong redirect https - http - never redirect https to http F https://198.58.118.167/ 198.58.118.167 http://198.58.118.167/ Wrong redirect https - http - never redirect https to http 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. N https://45.33.2.79/ 45.33.2.79 http://45.33.2.79/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://45.33.18.44/ 45.33.18.44 http://45.33.18.44/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://45.33.20.235/ 45.33.20.235 http://45.33.20.235/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://45.33.23.183/ 45.33.23.183 http://45.33.23.183/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://45.33.30.197/ 45.33.30.197 http://45.33.30.197/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://45.56.79.23/ 45.56.79.23 http://45.56.79.23/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://45.79.19.196/ 45.79.19.196 http://45.79.19.196/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://72.14.178.174/ 72.14.178.174 http://72.14.178.174/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://72.14.185.43/ 72.14.185.43 http://72.14.185.43/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://96.126.123.244/ 96.126.123.244 http://96.126.123.244/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://173.255.194.134/ 173.255.194.134 http://173.255.194.134/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors N https://198.58.118.167/ 198.58.118.167 http://198.58.118.167/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors X Fatal error: Nameserver doesn't support TCP connection: ns1.giantpanda.com / 139.144.190.86: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.giantpanda.com / 139.144.190.94: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.mytrafficmanagement.com: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.mytrafficmanagement.com / 139.144.190.86: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.mytrafficmanagement.com / 139.144.190.94: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.giantpanda.com / 139.144.190.112: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.giantpanda.com / 139.144.190.95: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.mytrafficmanagement.com: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.mytrafficmanagement.com / 139.144.190.112: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.mytrafficmanagement.com / 139.144.190.95: Timeout Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain how.com, 12 ip addresses, 2 different http results. Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain www.how.com, 12 ip addresses, 2 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain how.com, 12 ip addresses. 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.how.com, 12 ip addresses. A Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.how.com B Bad: _mta-sts TXT found, but invalid 2. Header-Checks U No https result with http status 2** or 4** (standard-check) found, no header checked. 3. DNS- and NameServer - Checks A Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 13 Queries complete, 9 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. 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:: 2 different Name Servers found: ns1.mytrafficmanagement.com, ns2.mytrafficmanagement.com, 2 Name Servers included in Delegation: ns1.mytrafficmanagement.com, ns2.mytrafficmanagement.com, 2 Name Servers included in 1 Zone definitions: ns1.mytrafficmanagement.com, ns2.mytrafficmanagement.com, 1 Name Servers listed in SOA.Primary: ns1.mytrafficmanagement.com. A Good: Only one SOA.Primary Name Server found.: ns1.mytrafficmanagement.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1.mytrafficmanagement.com. A Good: All Name Server Domain Names have a Public Suffix. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 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.: 4 Name Servers, 1 Top Level Domain: com A Good: Name Servers with different domain names found.: 2 different Domains found Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US A A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates A Good: Nameserver supports Echo Capitalization: 8 good Nameserver X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.giantpanda.com X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.mytrafficmanagement.com X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.giantpanda.com X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.mytrafficmanagement.com Nameserver doesn't pass all EDNS-Checks: ns1.giantpanda.com / 139.144.190.86: 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. Nameserver doesn't pass all EDNS-Checks: ns1.giantpanda.com / 139.144.190.94: 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. Nameserver doesn't pass all EDNS-Checks: ns1.mytrafficmanagement.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. Nameserver doesn't pass all EDNS-Checks: ns1.mytrafficmanagement.com / 139.144.190.86: 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. Nameserver doesn't pass all EDNS-Checks: ns1.mytrafficmanagement.com / 139.144.190.94: 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. Nameserver doesn't pass all EDNS-Checks: ns2.giantpanda.com / 139.144.190.95: 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. Nameserver doesn't pass all EDNS-Checks: ns2.giantpanda.com / 139.144.190.112: 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. Nameserver doesn't pass all EDNS-Checks: ns2.mytrafficmanagement.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. Nameserver doesn't pass all EDNS-Checks: ns2.mytrafficmanagement.com / 139.144.190.95: 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. Nameserver doesn't pass all EDNS-Checks: ns2.mytrafficmanagement.com / 139.144.190.112: 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 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: 698583 milliseconds, 698.583 seconds