1. General Results, most used to calculate the result A name "facasbrasil.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: 63591 (complete: 175327) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: facasbrasil.com has 2 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: facasbrasil.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A Good: one preferred version: www is preferred 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):7 complete Content-Type - header (9 urls) http://facasbrasil.com/ 34.102.136.180 Url with incomplete Content-Type - header - missing charset http://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 Url with incomplete Content-Type - header - missing charset A http://www.facasbrasil.com/ 34.226.34.219 https://www.facasbrasil.com/ Correct redirect http - https with the same domain name A http://www.facasbrasil.com/ 35.169.197.235 https://www.facasbrasil.com/ Correct redirect http - https with the same domain name B https://www.facasbrasil.com/ 34.226.34.219 Missing HSTS-Header B https://www.facasbrasil.com/ 35.169.197.235 Missing HSTS-Header B https://www.facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Missing HSTS-Header http://facasbrasil.com/ 34.102.136.180 system=PW;Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 country=DE;Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 city="";Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 traffic_target=gd;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 system=PW;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 country=DE;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 city="";Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 traffic_target=gd;Path=/;Max-Age=86400; 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 http://facasbrasil.com/ 34.102.136.180 system=PW;Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 country=DE;Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 city="";Path=/;Max-Age=86400; 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://facasbrasil.com/ 34.102.136.180 traffic_target=gd;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 system=PW;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 country=DE;Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 city="";Path=/;Max-Age=86400; 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://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 traffic_target=gd;Path=/;Max-Age=86400; 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. 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. E http://facasbrasil.com/ 54.232.92.235 https://www.facasbrasil.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. 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. I https://www.facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part. I http://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it. K http://facasbrasil.com/ 34.102.136.180, Status 200 http://facasbrasil.com/ 54.232.92.235, Status 301 Configuration problem - different ip addresses with different status K https://facasbrasil.com/ 34.102.136.180, Status -4 https://facasbrasil.com/ 54.232.92.235, Status -14 Configuration problem - different ip addresses with different status K http://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180, Status 200 http://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 54.232.92.235, Status 301 Configuration problem - different ip addresses with different status K http://facasbrasil.com:443/ 34.102.136.180, Status -8 http://facasbrasil.com:443/ 54.232.92.235, Status -14 Configuration problem - different ip addresses with different status M https://34.226.34.219/ 34.226.34.219 Misconfiguration - main pages should never send http status 400 - 499 M https://35.169.197.235/ 35.169.197.235 Misconfiguration - main pages should never send http status 400 - 499 N https://www.facasbrasil.com/ 34.226.34.219 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://www.facasbrasil.com/ 35.169.197.235 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://www.facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://34.226.34.219/ 34.226.34.219 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://35.169.197.235/ 35.169.197.235 Error - Certificate isn't trusted, RemoteCertificateNameMismatch Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain facasbrasil.com, 2 ip addresses, 2 different http results. 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 facasbrasil.com, 2 ip addresses. 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) 3. DNS- and NameServer - Checks A Info:: 33 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 33 Queries complete, 33 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Bad (greater 8):: An average of 8.3 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: amir.ns.cloudflare.com, nadia.ns.cloudflare.com, ns67.domaincontrol.com, ns68.domaincontrol.com, 2 Name Servers included in Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, 4 Name Servers included in 2 Zone definitions: amir.ns.cloudflare.com, nadia.ns.cloudflare.com, amir.ns.cloudflare.com, nadia.ns.cloudflare.com, ns67.domaincontrol.com, ns68.domaincontrol.com, 2 Name Servers listed in SOA.Primary: amir.ns.cloudflare.com, ns67.domaincontrol.com. Error: Different SOA.Primary Name Servers found, different SOA Definitions.: amir.ns.cloudflare.com,ns67.domaincontrol.com. Error: SOA.Primary Name Server not included in the delegation set.: amir.ns.cloudflare.com,ns67.domaincontrol.com. 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.: amir.ns.cloudflare.com (108.162.193.62): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: amir.ns.cloudflare.com (172.64.33.62): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: amir.ns.cloudflare.com (173.245.59.62): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: amir.ns.cloudflare.com (2606:4700:58::adf5:3b3e): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: amir.ns.cloudflare.com (2803:f800:50::6ca2:c13e): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: amir.ns.cloudflare.com (2a06:98c1:50::ac40:213e): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: nadia.ns.cloudflare.com (108.162.192.207): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: nadia.ns.cloudflare.com (172.64.32.207): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: nadia.ns.cloudflare.com (173.245.58.207): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: nadia.ns.cloudflare.com (2606:4700:50::adf5:3acf): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: nadia.ns.cloudflare.com (2803:f800:50::6ca2:c0cf): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: nadia.ns.cloudflare.com (2a06:98c1:50::ac40:20cf): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. Name Servers defined in Delegation, missing in Zone: ns67.domaincontrol.com, ns68.domaincontrol.com.Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: ns67.domaincontrol.com (97.74.103.44): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com, ns67.domaincontrol.com, ns68.domaincontrol.com. Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: ns67.domaincontrol.com (2603:5:2174::2c): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com, ns67.domaincontrol.com, ns68.domaincontrol.com. Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: ns68.domaincontrol.com (173.201.71.44): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com, ns67.domaincontrol.com, ns68.domaincontrol.com. Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.ns.cloudflare.com. 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.: ns68.domaincontrol.com (2603:5:2274::2c): Delegation: ns67.domaincontrol.com, ns68.domaincontrol.com, Zone: amir.ns.cloudflare.com, nadia.ns.cloudflare.com, ns67.domaincontrol.com, ns68.domaincontrol.com. Name Servers defined in Zone, missing in Delegation: amir.ns.cloudflare.com, nadia.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: 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 A Good: Name servers with different Country locations found: 4 Name Servers, 4 Countries: CA, CR, GB, US A Info: Ipv4-Subnet-list: 8 Name Servers, 4 different subnets (first Byte): 108., 172., 173., 97., 5 different subnets (first two Bytes): 108.162., 172.64., 173.201., 173.245., 97.74., 8 different subnets (first three Bytes): 108.162.192., 108.162.193., 172.64.32., 172.64.33., 173.201.71., 173.245.58., 173.245.59., 97.74.103. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 8 Name Servers with IPv6, 4 different subnets (first block): 2603:, 2606:, 2803:, 2a06:, 4 different subnets (first two blocks): 2603:0005:, 2606:4700:, 2803:f800:, 2a06:98c1:, 6 different subnets (first three blocks): 2603:0005:2174:, 2603:0005:2274:, 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 6 different subnets (first four blocks): 2603:0005:2174:0000:, 2603:0005:2274:0000:, 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: 16 good Nameserver A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates A Good: Nameserver supports Echo Capitalization: 16 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 16 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 16 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns-609.awsdns-12.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. Nameserver doesn't pass all EDNS-Checks: ns-609.awsdns-12.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. X Fatal error: Nameservers with different SOA Serial Numbers 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 http://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.226.34.219 Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.169.197.235 Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://www.facasbrasil.com/ 34.226.34.219 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://www.facasbrasil.com/ 35.169.197.235 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://www.facasbrasil.com/ 34.226.34.219 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.facasbrasil.com/ 35.169.197.235 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. A Good: Every https connection via port 443 supports the http/2 protocol via ALPN. https://www.facasbrasil.com/ 34.226.34.219 Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async. https://www.facasbrasil.com/ 35.169.197.235 Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async. http://facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180 Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async. https://www.facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 1 external CSS / JavaScript files without GZip found - 23 with GZip, 24 complete A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 6 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 5 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 19 with Cache-Control max-age too short (minimum 7 days), 2 with Cache-Control long enough, 26 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 6 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 6 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: All img-elements have a valid alt-attribute.: 6 img-elements found. 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 https://www.facasbrasil.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 20.313 seconds Warning: 404 needs more then one second https://34.226.34.219/ 34.226.34.219 4.080 seconds Warning: 404 needs more then one second https://35.169.197.235/ 35.169.197.235 4.007 seconds Warning: 404 needs more then one second A Info: Different Server-Headers found A Duration: 249644 milliseconds, 249.644 seconds