1. General Results, most used to calculate the result A name "hyatt.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: 83852 (complete: 216710) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: hyatt.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: hyatt.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A HSTS max-age is short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found, but not a problem because domain has an old preload-entry (Google-Policy: custom) A Excellent: Domain is in the Google-Preload-List A Excellent: Domain is in the Mozilla/Firefox-Preload-List A HSTS-Preload-Status: Preloaded. 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://hyatt.com/ 2.16.241.72 source-country=DE; path=/ 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://hyatt.com/ 2.16.241.83 source-country=DE; path=/ 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://hyatt.com/ 88.221.221.81 source-country=DE; path=/ 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://hyatt.com/ 88.221.221.115 source-country=DE; path=/ 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.hyatt.com/ 2.16.241.72 source-country=DE; path=/ 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.hyatt.com/ 2.16.241.83 source-country=DE; path=/ 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://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.72 source-country=DE; path=/ 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://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.83 source-country=DE; path=/ 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://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.81 source-country=DE; path=/ 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://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.115 source-country=DE; path=/ 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.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.72 source-country=DE; path=/ 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.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.83 source-country=DE; path=/ 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://hyatt.com/ 2.16.241.72 source-country=DE; path=/ Cookie sent via https, but not marked as secure B https://hyatt.com/ 2.16.241.83 source-country=DE; path=/ Cookie sent via https, but not marked as secure B https://hyatt.com/ 88.221.221.81 source-country=DE; path=/ Cookie sent via https, but not marked as secure B https://hyatt.com/ 88.221.221.115 source-country=DE; path=/ Cookie sent via https, but not marked as secure B https://www.hyatt.com/ 2.16.241.72 tkrm_alpekz_s1.3=0aAJMCw62ZHKJlJuTCze1ZQRetQgyQVZG5FtJTAGHbdCzIXCM8EEQjDV6Hd4hNAcXPAIJydbVam44yx5UoSlafLJkXObWDofkpWR0BrpYyYMHbBDPjvc36hyQ40UQcSup5T1FprNd50nyTcUi7s6BvDm; Max-Age=86400; Path=/; Expires=Sat, 28 Jan 2023 12:17:13 GMT; HttpOnly Cookie sent via https, but not marked as secure B https://www.hyatt.com/ 2.16.241.72 source-country=DE; path=/ Cookie sent via https, but not marked as secure B https://www.hyatt.com/ 2.16.241.83 tkrm_alpekz_s1.3=09uVQhT5O6IJ8F8JEi0mejABojw9xr0khpG2HOYn6CsM50nMzoriM2qkrpdPyZ4OCC4YOOXJO9oXCPjMHWvr8siJyNQtRfZnuH3MNJhgscjvZdgIhvKL6taZajK1WaM33p2tI4aDCqyDwkNDI3PGQAJN; Max-Age=86400; Path=/; Expires=Sat, 28 Jan 2023 12:17:18 GMT; HttpOnly Cookie sent via https, but not marked as secure B https://www.hyatt.com/ 2.16.241.83 source-country=DE; path=/ Cookie sent via https, but not marked as secure B https://www.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de source-country=DE; path=/ Cookie sent via https, but not marked as secure B http://hyatt.com/ 2.16.241.72 source-country=DE; 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 http://hyatt.com/ 2.16.241.83 source-country=DE; 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 http://hyatt.com/ 88.221.221.81 source-country=DE; 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 http://hyatt.com/ 88.221.221.115 source-country=DE; 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 http://www.hyatt.com/ 2.16.241.72 source-country=DE; 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 http://www.hyatt.com/ 2.16.241.83 source-country=DE; 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://hyatt.com/ 2.16.241.72 source-country=DE; 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://hyatt.com/ 2.16.241.83 source-country=DE; 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://hyatt.com/ 88.221.221.81 source-country=DE; 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://hyatt.com/ 88.221.221.115 source-country=DE; 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.hyatt.com/ 2.16.241.72 tkrm_alpekz_s1.3=0aAJMCw62ZHKJlJuTCze1ZQRetQgyQVZG5FtJTAGHbdCzIXCM8EEQjDV6Hd4hNAcXPAIJydbVam44yx5UoSlafLJkXObWDofkpWR0BrpYyYMHbBDPjvc36hyQ40UQcSup5T1FprNd50nyTcUi7s6BvDm; Max-Age=86400; Path=/; Expires=Sat, 28 Jan 2023 12:17:13 GMT; 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://www.hyatt.com/ 2.16.241.72 source-country=DE; 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.hyatt.com/ 2.16.241.83 tkrm_alpekz_s1.3=09uVQhT5O6IJ8F8JEi0mejABojw9xr0khpG2HOYn6CsM50nMzoriM2qkrpdPyZ4OCC4YOOXJO9oXCPjMHWvr8siJyNQtRfZnuH3MNJhgscjvZdgIhvKL6taZajK1WaM33p2tI4aDCqyDwkNDI3PGQAJN; Max-Age=86400; Path=/; Expires=Sat, 28 Jan 2023 12:17:18 GMT; 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://www.hyatt.com/ 2.16.241.83 source-country=DE; 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 http://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.72 source-country=DE; 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 http://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.83 source-country=DE; 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 http://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.81 source-country=DE; 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 http://hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.115 source-country=DE; 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 http://www.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.72 source-country=DE; 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 http://www.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.83 source-country=DE; 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.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de vrid=rBEAA2PTwN8M7AA5KXGqAg==; expires=Mon, 26-Jan-26 12:17:35 GMT; domain=hyatt.com; path=/; Secure; 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://www.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de source-country=DE; 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. C Error - no version with Http-Status 200 H Fatal error: No https - result with http-status 200, no encryption M https://www.hyatt.com/ 2.16.241.72 Misconfiguration - main pages should never send http status 400 - 499 M https://www.hyatt.com/ 2.16.241.83 Misconfiguration - main pages should never send http status 400 - 499 P https://2.16.241.72/ 2.16.241.72 Error creating a TLS-Connection: No more details available. P https://2.16.241.83/ 2.16.241.83 Error creating a TLS-Connection: No more details available. P https://88.221.221.81/ 88.221.221.81 Error creating a TLS-Connection: No more details available. P https://88.221.221.115/ 88.221.221.115 Error creating a TLS-Connection: No more details available. A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain hyatt.com, 2 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 hyatt.com, 2 ip addresses. B No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.hyatt.com 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) F www.hyatt.com 2.16.241.72 Content-Security-Policy Critical: Missing Header: F www.hyatt.com 2.16.241.72 X-Content-Type-Options Critical: Missing Header: F www.hyatt.com 2.16.241.72 Referrer-Policy Critical: Missing Header: F www.hyatt.com 2.16.241.72 Permissions-Policy Critical: Missing Header: F www.hyatt.com 2.16.241.83 Content-Security-Policy Critical: Missing Header: F www.hyatt.com 2.16.241.83 X-Content-Type-Options Critical: Missing Header: F www.hyatt.com 2.16.241.83 Referrer-Policy Critical: Missing Header: F www.hyatt.com 2.16.241.83 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 19 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers. A Info:: 19 Queries complete, 19 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 3.2 queries per domain name server required to find all ip addresses of all name servers. A Info:: 7 different Name Servers found: a10-64.akam.net, a13-65.akam.net, a1-77.akam.net, a24-66.akam.net, a6-67.akam.net, a7-64.akam.net, iapibgm.orrdc.hyattsys.net, 6 Name Servers included in Delegation: a1-77.akam.net, a10-64.akam.net, a13-65.akam.net, a24-66.akam.net, a6-67.akam.net, a7-64.akam.net, 6 Name Servers included in 2 Zone definitions: a1-77.akam.net, a10-64.akam.net, a13-65.akam.net, a24-66.akam.net, a6-67.akam.net, a7-64.akam.net, 1 Name Servers listed in SOA.Primary: iapibgm.orrdc.hyattsys.net. A Good: Only one SOA.Primary Name Server found.: iapibgm.orrdc.hyattsys.net. Error: SOA.Primary Name Server not included in the delegation set.: iapibgm.orrdc.hyattsys.net. 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: a1-77.akam.net, a10-64.akam.net, a13-65.akam.net, a24-66.akam.net, a6-67.akam.net, a7-64.akam.net A Good: All Name Server Domain Names have a Public Suffix. Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1 A Good: Minimal 2 different name servers (public suffix and public ip address) found: 6 different Name Servers found A Good: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (2 Name Servers without IPv6) 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.: 6 Name Servers, 1 Top Level Domain: net A Good: Name Servers with different domain names found.: 2 different Domains found A Good: Name servers with different Country locations found: 6 Name Servers, 5 Countries: AT, DE, ES, NL, US A Info: Ipv4-Subnet-list: 6 Name Servers, 4 different subnets (first Byte): 193., 2., 23., 96., 6 different subnets (first two Bytes): 193.108., 2.16., 2.22., 23.211., 23.61., 96.7., 6 different subnets (first three Bytes): 193.108.91., 2.16.130., 2.22.230., 23.211.133., 23.61.199., 96.7.50. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 3 different subnets (first two blocks): 2600:1401:, 2600:1406:, 2600:1480:, 4 different subnets (first three blocks): 2600:1401:0001:, 2600:1401:0002:, 2600:1406:0032:, 2600:1480:0800:, 4 different subnets (first four blocks): 2600:1401:0001:0000:, 2600:1401:0002:0000:, 2600:1406:0032:0000:, 2600:1480:0800:0000: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 10 good Nameserver A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates A Good: Nameserver supports Echo Capitalization: 10 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 10 good Nameserver Nameserver doesn't pass all EDNS-Checks: iapibgm.orrdc.hyattsys.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: ns1-2.akamai.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-2.akamai.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. A Good: All SOA have the same Serial Number A Good: CAA entries found, creating certificate is limited: entrust.net is allowed to create certificates 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 https://www.hyatt.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.937 seconds Warning: 404 needs more then one second A Duration: 316160 milliseconds, 316.160 seconds