| 1. General Results, most used to calculate the result |
| A | name "bloomydesign.it" is domain, public suffix is ".it", top-level-domain is ".it", top-level-domain-type is "country-code", Country is Italy, tld-manager is "IIT - CNR", num .it-domains preloaded: 1182 (complete: 151507)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: bloomydesign.it has only one ip address.
|
| Warning: Only one ip address found: www.bloomydesign.it 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: bloomydesign.it 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.bloomydesign.it has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: destination is https
|
| 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 (4 urls)
|
| https://bloomydesign.it/ 185.4.142.32
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.bloomydesign.it/ 185.4.142.32
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.bloomydesign.it/404.shtml
|
| Url with incomplete Content-Type - header - missing charset
|
| https://185.4.142.32/ 185.4.142.32
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://bloomydesign.it/ 185.4.142.32
|
| Missing HSTS-Header
|
| B | https://www.bloomydesign.it/ 185.4.142.32
|
| Missing HSTS-Header
|
| B | https://www.bloomydesign.it/404.shtml
|
| Missing HSTS-Header
|
| http://bloomydesign.it/ 185.4.142.32
| cookiesession1=4D0FEAABBTLQFMJYNK4VITRRAJSQF097;Path=/;HttpOnly
| 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.bloomydesign.it/ 185.4.142.32
| cookiesession1=4D0FEAABSYKPFGWMBY2OOBNZDXDU9FB3;Path=/;HttpOnly
| 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://bloomydesign.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.4.142.32
| cookiesession1=4D0FEAABJ9728MXVFVLST8VUDUKJ6640;Path=/;HttpOnly
| 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.bloomydesign.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.4.142.32
| cookiesession1=4D0FEAAB9Y0IT5J3ALERYTZI7LZH6D5F;Path=/;HttpOnly
| 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://185.4.142.32/ 185.4.142.32
| cookiesession1=4D0FEAAEHGEPCJ1X6X9VH4EK3CYXE35E;Path=/;HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | http://bloomydesign.it/ 185.4.142.32
| cookiesession1=4D0FEAABBTLQFMJYNK4VITRRAJSQF097;Path=/;HttpOnly
| 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 | http://www.bloomydesign.it/ 185.4.142.32
| cookiesession1=4D0FEAABSYKPFGWMBY2OOBNZDXDU9FB3;Path=/;HttpOnly
| 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 | http://bloomydesign.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.4.142.32
| cookiesession1=4D0FEAABJ9728MXVFVLST8VUDUKJ6640;Path=/;HttpOnly
| 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 | http://www.bloomydesign.it/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.4.142.32
| cookiesession1=4D0FEAAB9Y0IT5J3ALERYTZI7LZH6D5F;Path=/;HttpOnly
| 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://185.4.142.32/ 185.4.142.32
| cookiesession1=4D0FEAAEHGEPCJ1X6X9VH4EK3CYXE35E;Path=/;HttpOnly
| 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.
|
| M | https://bloomydesign.it/ 185.4.142.32
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://www.bloomydesign.it/ 185.4.142.32
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://bloomydesign.it/ 185.4.142.32
|
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://www.bloomydesign.it/ 185.4.142.32
|
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://www.bloomydesign.it/404.shtml
|
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://185.4.142.32/ 185.4.142.32
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.4.142.32:2087
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | 185.4.142.32:2222
|
| 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain bloomydesign.it, 1 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.bloomydesign.it, 1 ip addresses.
|
| 2. Header-Checks |
| 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.slhosting.biz (94.102.134.61), ns2.slhosting.biz (80.244.118.77)
|
| 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.slhosting.biz, ns2.slhosting.biz, 2 Name Servers included in Delegation: ns1.slhosting.biz, ns2.slhosting.biz, 2 Name Servers included in 1 Zone definitions: ns1.slhosting.biz, ns2.slhosting.biz, 1 Name Servers listed in SOA.Primary: ns1.slhosting.biz.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.slhosting.biz.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.slhosting.biz.
|
| 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.slhosting.biz, ns2.slhosting.biz
|
| 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: 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: biz
|
| 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: slhosting.biz
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: IT
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 80., 94., 2 different subnets (first two Bytes): 80.244., 94.102., 2 different subnets (first three Bytes): 80.244.118., 94.102.134.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| 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: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 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 |
| https://www.bloomydesign.it/404.shtml
|
| 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.
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| A | Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| https://185.4.142.32/ 185.4.142.32
|
| 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 | 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: 84286 milliseconds, 84.286 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)