1. General Results, most used to calculate the result A name "ihg.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: ihg.com has 4 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: ihg.com has 2 ipv4, 2 ipv6 addresses A Good: No asked Authoritative Name Server had a timeout A Good: every cookie sent via https is marked as secure A Good: HSTS has preload directive Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive. 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 (24 urls) http://ihg.com/ 2.16.241.137 Url with incomplete Content-Type - header - missing charset http://ihg.com/ 2.16.241.157 Url with incomplete Content-Type - header - missing charset http://ihg.com/ 88.221.221.74 Url with incomplete Content-Type - header - missing charset http://ihg.com/ 88.221.221.83 Url with incomplete Content-Type - header - missing charset http://ihg.com/ 2a02:26f0:12d::58dd:dd4a Url with incomplete Content-Type - header - missing charset http://ihg.com/ 2a02:26f0:12d::58dd:dd52 Url with incomplete Content-Type - header - missing charset http://www.ihg.com/ 2.16.241.137 Url with incomplete Content-Type - header - missing charset http://www.ihg.com/ 2.16.241.157 Url with incomplete Content-Type - header - missing charset https://ihg.com/ 2.16.241.137 Url with incomplete Content-Type - header - missing charset https://ihg.com/ 2.16.241.157 Url with incomplete Content-Type - header - missing charset https://ihg.com/ 88.221.221.74 Url with incomplete Content-Type - header - missing charset https://ihg.com/ 88.221.221.83 Url with incomplete Content-Type - header - missing charset https://ihg.com/ 2a02:26f0:12d::58dd:dd4a Url with incomplete Content-Type - header - missing charset https://ihg.com/ 2a02:26f0:12d::58dd:dd52 Url with incomplete Content-Type - header - missing charset https://www.ihg.com/ 2.16.241.137 Url with incomplete Content-Type - header - missing charset https://www.ihg.com/ 2.16.241.157 Url with incomplete Content-Type - header - missing charset http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 Url with incomplete Content-Type - header - missing charset http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 Url with incomplete Content-Type - header - missing charset http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 Url with incomplete Content-Type - header - missing charset http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 Url with incomplete Content-Type - header - missing charset http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a Url with incomplete Content-Type - header - missing charset http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 Url with incomplete Content-Type - header - missing charset http://www.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 Url with incomplete Content-Type - header - missing charset http://www.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 Url with incomplete Content-Type - header - missing charset B Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found http://ihg.com/ 2.16.241.137 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/ 2.16.241.137 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2.16.241.137 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 2.16.241.137 roomKeyCookie=1674834162; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2.16.241.137 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2.16.241.157 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/ 2.16.241.157 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2.16.241.157 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 2.16.241.157 roomKeyCookie=1674834163; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2.16.241.157 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 88.221.221.74 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/ 88.221.221.74 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/ 88.221.221.74 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/ 88.221.221.74 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 88.221.221.74 roomKeyCookie=1674834163; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 88.221.221.74 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 88.221.221.83 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/ 88.221.221.83 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/ 88.221.221.83 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/ 88.221.221.83 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 88.221.221.83 roomKeyCookie=1674834163; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 88.221.221.83 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a roomKeyCookie=1674834163; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 roomKeyCookie=1674834163; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/ 2.16.241.137 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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.ihg.com/ 2.16.241.137 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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.ihg.com/ 2.16.241.137 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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.ihg.com/ 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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.ihg.com/ 2.16.241.137 roomKeyCookie=1674834163; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/ 2.16.241.137 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/ 2.16.241.157 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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.ihg.com/ 2.16.241.157 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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.ihg.com/ 2.16.241.157 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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.ihg.com/ 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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.ihg.com/ 2.16.241.157 roomKeyCookie=1674834163; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/ 2.16.241.157 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 roomKeyCookie=1674834193; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 roomKeyCookie=1674834194; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 roomKeyCookie=1674834194; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 roomKeyCookie=1674834195; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a roomKeyCookie=1674834195; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 roomKeyCookie=1674834195; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 roomKeyCookie=1674834195; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 akamaiCountryCode=DE; path=/; secure; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 akamaiIsWirelessDevice=false; path=/; secure; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 akamaiIsTablet=false; path=/; secure; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 roomKeyCookie=1674834196; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 CopterConnect=B229BB78-65EB-4128-9562-6BEC44A1811F%7Cae020d407073c7e711f5649ef9844ec4%7CIHGRoomkeypop; domain=.ihg.com; secure; HttpOnly; SameSite=Strict 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://ihg.com/ 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 88.221.221.74 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 88.221.221.83 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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.ihg.com/ 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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.ihg.com/ 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 88.221.221.74 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 88.221.221.83 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/ 2a02:26f0:12d::58dd:dd4a X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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://ihg.com/ 2a02:26f0:12d::58dd:dd52 X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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.ihg.com/ 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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.ihg.com/ 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 X-IHG-TrueClient_IP=2a01:238:301b::1227; path=/; secure 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 X-IHG-TrueClient_IP=85.215.2.227; path=/; secure 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 http://ihg.com/ 2.16.241.137 Misconfiguration - main pages should never send http status 400 - 499 M http://ihg.com/ 2.16.241.157 Misconfiguration - main pages should never send http status 400 - 499 M http://ihg.com/ 88.221.221.74 Misconfiguration - main pages should never send http status 400 - 499 M http://ihg.com/ 88.221.221.83 Misconfiguration - main pages should never send http status 400 - 499 M http://ihg.com/ 2a02:26f0:12d::58dd:dd4a Misconfiguration - main pages should never send http status 400 - 499 M http://ihg.com/ 2a02:26f0:12d::58dd:dd52 Misconfiguration - main pages should never send http status 400 - 499 M http://www.ihg.com/ 2.16.241.137 Misconfiguration - main pages should never send http status 400 - 499 M http://www.ihg.com/ 2.16.241.157 Misconfiguration - main pages should never send http status 400 - 499 M https://ihg.com/ 2.16.241.137 Misconfiguration - main pages should never send http status 400 - 499 M https://ihg.com/ 2.16.241.157 Misconfiguration - main pages should never send http status 400 - 499 M https://ihg.com/ 88.221.221.74 Misconfiguration - main pages should never send http status 400 - 499 M https://ihg.com/ 88.221.221.83 Misconfiguration - main pages should never send http status 400 - 499 M https://ihg.com/ 2a02:26f0:12d::58dd:dd4a Misconfiguration - main pages should never send http status 400 - 499 M https://ihg.com/ 2a02:26f0:12d::58dd:dd52 Misconfiguration - main pages should never send http status 400 - 499 M https://www.ihg.com/ 2.16.241.137 Misconfiguration - main pages should never send http status 400 - 499 M https://www.ihg.com/ 2.16.241.157 Misconfiguration - main pages should never send http status 400 - 499 P https://2.16.241.137/ 2.16.241.137 Error creating a TLS-Connection: No more details available. P https://2.16.241.157/ 2.16.241.157 Error creating a TLS-Connection: No more details available. P https://88.221.221.74/ 88.221.221.74 Error creating a TLS-Connection: No more details available. P https://88.221.221.83/ 88.221.221.83 Error creating a TLS-Connection: No more details available. P https://[2a02:26f0:012d:0000:0000:0000:58dd:dd4a]/ 2a02:26f0:12d::58dd:dd4a Error creating a TLS-Connection: No more details available. P https://[2a02:26f0:012d:0000:0000:0000:58dd:dd52]/ 2a02:26f0:12d::58dd:dd52 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 ihg.com, 4 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 ihg.com, 4 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.ihg.com 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) A ihg.com 2.16.241.137 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A ihg.com 2.16.241.157 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A ihg.com 88.221.221.74 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A ihg.com 88.221.221.83 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A ihg.com 2a02:26f0:12d::58dd:dd4a Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A ihg.com 2a02:26f0:12d::58dd:dd52 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A www.ihg.com 2.16.241.137 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff A www.ihg.com 2.16.241.157 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.kayak.com https://www.kayak.com.ar https://www.kayak.com.au https://www.kayak.bo https://www.kayak.com.br https://www.kayak.cat https://www.kayak.cl https://www.cn.kayak.com https://www.kayak.com.co https://www.kayak.co.cr https://www.kayak.dk https://www.kayak.com.do https://www.kayak.com.ec https://www.kayak.com.sv https://www.kayak.fr https://www.kayak.de https://www.kayak.com.gt https://www.kayak.com.hn https://www.kayak.com.hk https://www.kayak.co.in https://www.kayak.co.id https://www.kayak.ie https://www.kayak.it https://www.kayak.co.jp https://www.kayak.com.my https://www.kayak.com.mx https://www.kayak.nl https://www.kayak.com.ni https://www.kayak.no https://www.kayak.com.pa https://www.kayak.com.py https://www.kayak.com.pe https://www.kayak.com.ph https://www.kayak.pl https://www.kayak.pt https://www.kayak.com.pr https://www.en.kayak.sa https://www.kayak.sg https://www.kayak.co.kr https://www.kayak.es https://www.kayak.se https://www.kayak.ch https://www.kayak.co.th https://www.kayak.com.tr https://www.kayak.ae https://www.kayak.co.uk https://www.kayak.com.uy https://www.kayak.co.ve F Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that. E Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used. A Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used. E Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required. F Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff F ihg.com 2.16.241.137 Referrer-Policy Critical: Missing Header: F ihg.com 2.16.241.137 Permissions-Policy Critical: Missing Header: F ihg.com 2.16.241.157 Referrer-Policy Critical: Missing Header: F ihg.com 2.16.241.157 Permissions-Policy Critical: Missing Header: F ihg.com 88.221.221.74 Referrer-Policy Critical: Missing Header: F ihg.com 88.221.221.74 Permissions-Policy Critical: Missing Header: F ihg.com 88.221.221.83 Referrer-Policy Critical: Missing Header: F ihg.com 88.221.221.83 Permissions-Policy Critical: Missing Header: F ihg.com 2a02:26f0:12d::58dd:dd4a Referrer-Policy Critical: Missing Header: F ihg.com 2a02:26f0:12d::58dd:dd4a Permissions-Policy Critical: Missing Header: F ihg.com 2a02:26f0:12d::58dd:dd52 Referrer-Policy Critical: Missing Header: F ihg.com 2a02:26f0:12d::58dd:dd52 Permissions-Policy Critical: Missing Header: F www.ihg.com 2.16.241.137 Referrer-Policy Critical: Missing Header: F www.ihg.com 2.16.241.137 Permissions-Policy Critical: Missing Header: F www.ihg.com 2.16.241.157 Referrer-Policy Critical: Missing Header: F www.ihg.com 2.16.241.157 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 26 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 7 Name Servers. A Info:: 26 Queries complete, 26 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 3.7 queries per domain name server required to find all ip addresses of all name servers. A Info:: 7 different Name Servers found: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net, 6 Name Servers included in Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, 6 Name Servers included in 1 Zone definitions: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net, 1 Name Servers listed in SOA.Primary: a1-131.akam.net. A Good: Only one SOA.Primary Name Server found.: a1-131.akam.net. A Good: SOA.Primary Name Server included in the delegation set.: a1-131.akam.net. 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.: a1-131.akam.net (193.108.91.131): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a1-131.akam.net (2600:1401:2::83): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a16-66.akam.net (23.211.132.66): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a16-66.akam.net (2600:1406:1b::42): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a26-67.akam.net (23.74.25.67): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a28-64.akam.net (95.100.173.64): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a4-64.akam.net (72.246.46.64): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a5-65.akam.net (95.100.168.65): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a5-65.akam.net (2600:1480:b000::41): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a9-66.akam.net (184.85.248.66): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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.: a9-66.akam.net (2a02:26f0:117::42): Delegation: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a5-65.akam.net, a9-66.akam.net, Zone: a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net. Name Servers defined in Delegation, missing in Zone: a28-64.akam.net.Name Servers defined in Zone, missing in Delegation: a4-64.akam.net. 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: 7 different Name Servers found A Good: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (3 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.: 7 Name Servers, 1 Top Level Domain: net 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: akam.net A Good: Name servers with different Country locations found: 7 Name Servers, 7 Countries: AT, DE, FR, IT, NL, PL, US A Info: Ipv4-Subnet-list: 7 Name Servers, 5 different subnets (first Byte): 184., 193., 23., 72., 95., 6 different subnets (first two Bytes): 184.85., 193.108., 23.211., 23.74., 72.246., 95.100., 7 different subnets (first three Bytes): 184.85.248., 193.108.91., 23.211.132., 23.74.25., 72.246.46., 95.100.168., 95.100.173. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2600:, 2a02:, 4 different subnets (first two blocks): 2600:1401:, 2600:1406:, 2600:1480:, 2a02:26f0:, 4 different subnets (first three blocks): 2600:1401:0002:, 2600:1406:001b:, 2600:1480:b000:, 2a02:26f0:0117:, 4 different subnets (first four blocks): 2600:1401:0002:0000:, 2600:1406:001b:0000:, 2600:1480:b000:0000:, 2a02:26f0:0117:0000: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 11 good Nameserver A Good: Nameserver supports Echo Capitalization: 11 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 11 good Nameserver Nameserver doesn't pass all EDNS-Checks: a16-66.akam.net / 23.211.132.66: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok. 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 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://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 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. http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 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. http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.74 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. http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.221.221.83 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. http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd4a 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. http://ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:26f0:12d::58dd:dd52 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. http://www.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.137 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. http://www.ihg.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2.16.241.157 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 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: 483550 milliseconds, 483.550 seconds