1. General Results, most used to calculate the result A name "xnxx.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 89449 (complete: 231048) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: www.xnxx.com has 8 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: xnxx.com has 8 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: www.xnxx.com has no ipv6 address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: xnxx.com has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A Good: destination is https A Good - only one version with Http-Status 200 A Good: one preferred version: www is preferred A Good: No cookie sent via http. HSTS-Preload-Status: Rejected. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.Domain was added and removed without being preloaded. A Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):9 complete Content-Type - header (10 urls) http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Url with incomplete Content-Type - header - missing charset A http://www.xnxx.com/ 185.88.181.53 https://www.xnxx.com/ Correct redirect http - https with the same domain name A http://www.xnxx.com/ 185.88.181.54 https://www.xnxx.com/ Correct redirect http - https with the same domain name A http://www.xnxx.com/ 185.88.181.55 https://www.xnxx.com/ Correct redirect http - https with the same domain name A http://www.xnxx.com/ 185.88.181.56 https://www.xnxx.com/ Correct redirect http - https with the same domain name A http://www.xnxx.com/ 185.88.181.57 https://www.xnxx.com/ Correct redirect http - https with the same domain name A http://www.xnxx.com/ 185.88.181.58 https://www.xnxx.com/ Correct redirect http - https with the same domain name A http://www.xnxx.com/ 185.88.181.59 https://www.xnxx.com/ Correct redirect http - https with the same domain name A http://www.xnxx.com/ 185.88.181.60 https://www.xnxx.com/ Correct redirect http - https with the same domain name B https://xnxx.com/ 185.88.181.53 Missing HSTS-Header B https://xnxx.com/ 185.88.181.54 Missing HSTS-Header B https://xnxx.com/ 185.88.181.55 Missing HSTS-Header B https://xnxx.com/ 185.88.181.56 Missing HSTS-Header B https://xnxx.com/ 185.88.181.57 Missing HSTS-Header B https://xnxx.com/ 185.88.181.58 Missing HSTS-Header B https://xnxx.com/ 185.88.181.59 Missing HSTS-Header B https://xnxx.com/ 185.88.181.60 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.53 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.54 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.55 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.56 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.57 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.58 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.59 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.60 Missing HSTS-Header B https://www.xnxx.com/ 185.88.181.53 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.53 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.53 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.53 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.54 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.54 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.54 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.54 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.55 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.55 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.55 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.55 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.56 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.56 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.56 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.56 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.57 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.57 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.57 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.57 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.58 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.58 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.58 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.58 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.59 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.59 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.59 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.59 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.60 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.60 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.60 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.60 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com Cookie sent via https, but not marked as secure B https://www.xvideos.com/ _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xvideos.com Cookie sent via https, but not marked as secure B https://www.xvideos.com/ _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xvideos.com Cookie sent via https, but not marked as secure B https://www.xvideos.com/ _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xvideos.com Cookie sent via https, but not marked as secure B https://www.xnxx.com/ 185.88.181.53 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.53 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.53 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.53 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.53 session_token=0f389fbac6c5c08b1D9Pn7AqduRxJh1YfnBrutOlhlLo_VsPYeo_v8llmH6DZhD_PI8Iy-GQNRqFtPj_zQ4P85xmYYGphKRKZmRM0KUaBOTtYf2XBkqtTHqvBeF09OZHyz-VGFm93USBXWJ1S3KMQUQadRSp6QnhKhETp6qVWNsHGNNNLRUe_k_ixHtycRXlgH5hlriyWtDPHXze; expires=Tue, 31-Oct-2023 09:08:23 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xnxx.com/ 185.88.181.54 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.54 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.54 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.54 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.54 session_token=ad4c92268551d411qu0xZi2ot-YbwqYfS1s3VWDLF8Lgy30vR9MfIrWC57o1eM5T6a_LgBtY5FHOmO3R6J38fZIjLcTQrgzwgBFX96K4v5SwGJWZzVv5xDNCMz-32y1b8qPKPJB_s1qcCtDlz4WjL2unDsNHZibGgXTEuyN_A8wx3QDQOCEfqP2Eyvmi5UNF4awmH0xh7-9ucU7P; expires=Tue, 31-Oct-2023 09:08:27 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xnxx.com/ 185.88.181.55 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.55 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.55 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.55 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.55 session_token=85b0ce6eca16ba2foACiAOXb7sFTw8HITZXtSVMl5TQFtbcmDqFItbyXBvoccwG9BVFFFrO-iY4gAPMJchLcyv6BomA67pnOnth9IofBMXl0C5k-mf8FkiPcUScuCj0tdNzL1TzPY3A88Kf2lw-n-9be08QQ4K_avJekRQVQzcZSDKZDfjRFX4_XXsKPpsl1kyZ8pSi1Nphw0fud; expires=Tue, 31-Oct-2023 09:08:32 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xnxx.com/ 185.88.181.56 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.56 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.56 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.56 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.56 session_token=f16a12562b65a76bjqRjuiR6YUG0kMCAE8AC3k_c_jhtGFN6vGNtJdnBXqBSy9f_MKtFfuL7UJN2_rWvUoMYqcyOq_NrtSDvlPRQWX5f4x7vfxpJnu4GIM8g-gGKTPXtupiwtdDTjocwIp_B8bv_AQerlDTxl8_Uj9Uwx6gEu8GsYKPvEaCwuEiehYZs05jtLgb28d825kobhC0j; expires=Tue, 31-Oct-2023 09:08:36 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xnxx.com/ 185.88.181.57 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.57 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.57 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.57 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.57 session_token=5053b599f319972dCXy94hKxyYtwgqb51kEa0m-K4QtukfDg_5aOBlb62ajH5aGsexDuFko3sVd85yPjfwBR7cK20A443oJ9X9D3f9YBVarSkyqxg4NccqvgLWTHVHNj3u7ZUyojjaYm-lawZzUFG-3uK813Ve2xrFEYWGf9Wlpssx8aMmxL8uQ17PWDL4860LbKX0582h6P1x3m; expires=Tue, 31-Oct-2023 09:08:40 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xnxx.com/ 185.88.181.58 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.58 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.58 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.58 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.58 session_token=0e907b2181e290ef51kG9rzmZPHXoFqzJmdk6z_YzmWHXtf8MACobhfmHo8tb54VB_DEkPe9V0WfHcUsuq9aSW2liZ-Bko0KWzCK7qtpfQtYSM9JtbshjE1h86U2EhjSnhcP72j-uXD9E6Fkvc1WwxJLTlGmPMgEWqbVvW3wG4Xg-QVMxYSF7eKDUtO2QjQ0AiZ2dZuHTNpndgXf; expires=Tue, 31-Oct-2023 09:08:45 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xnxx.com/ 185.88.181.59 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.59 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.59 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.59 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.59 session_token=7d300ed7f45eaff3OzT-adblO2dxA0b9t4ImCS9NcIa1iXl8NxNTwfp8PsV9EFnuPuhSu5WoIpMRozWzVN2a3wN48eBT1C8QTdDDwpuQ_KIYNY4ciN4oCiifJI8szTF84qUAuAAd8SGhoI0QFC2R_r3opSMrnlwDpykOR2eFQNfjsV4jgb4EOruIVKndSqmCQcAvMSGTvMe6z2zm; expires=Tue, 31-Oct-2023 09:08:49 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xnxx.com/ 185.88.181.60 pending_thumb=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.60 _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.60 _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.60 _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xnxx.com 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.xnxx.com/ 185.88.181.60 session_token=bcbc2d23614634488qfs0FhPz0CjVXlvExcx6oADlGToOPcsSjF08NJ-s8HUj3EvGlU-TCs2ni3USjysNZ88RHnDJ47eJVhEWz0QoR7BKxGy-rX2xdli_utu6z384HadefFTqw-C8nSzjvNYBnyiWDqsaOeWTJPDUVjGTFku9DRBhj4rQ4t8BG9xTSnhEVkb0kZbzbDYpC3gK32n; expires=Tue, 31-Oct-2023 09:08:53 GMT; Max-Age=2592000; path=/; domain=.xnxx.com; 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.xvideos.com/ _ga=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xvideos.com 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.xvideos.com/ _gid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xvideos.com 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.xvideos.com/ _gat=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.xvideos.com 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.xvideos.com/ session_token=3e2c9602518fda84rZt1O0SmgIFK3tvzm_Qy5CMiIEigRtJKc8jS20iT1RhjPl-HUIIHSAcwBHVYA0xPl1c6BlgsIrd0mEDH2w7JByNoX_xt4epnEsLAks86ZAqzwvO5I3rqKbqbGLvvkUZWHS4gQZftcIyNvQW6OVi1kRJarL0gQYEHXp7AfPoPlPLbYgd7M6vokvovXR3JP9wJ; expires=Tue, 31-Oct-2023 09:10:04 GMT; Max-Age=2592000; path=/; domain=.xvideos.com; 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. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.53 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.54 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.55 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.56 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.57 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.58 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.59 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.60 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.53 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.54 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.55 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.56 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.57 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.58 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.59 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. D http://www.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.88.181.60 http://acme.xnxx.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.53 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.54 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.55 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.56 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.57 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.58 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.59 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. E http://xnxx.com/ 185.88.181.60 https://www.xnxx.com/ Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version. F https://185.88.181.53/ 185.88.181.53 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http F https://185.88.181.54/ 185.88.181.54 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http F https://185.88.181.55/ 185.88.181.55 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http F https://185.88.181.56/ 185.88.181.56 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http F https://185.88.181.57/ 185.88.181.57 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http F https://185.88.181.58/ 185.88.181.58 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http F https://185.88.181.59/ 185.88.181.59 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http F https://185.88.181.60/ 185.88.181.60 http://www.xvideos.com/ Wrong redirect https - http - never redirect https to http N https://185.88.181.53/ 185.88.181.53 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://185.88.181.54/ 185.88.181.54 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://185.88.181.55/ 185.88.181.55 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://185.88.181.56/ 185.88.181.56 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://185.88.181.57/ 185.88.181.57 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://185.88.181.58/ 185.88.181.58 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://185.88.181.59/ 185.88.181.59 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://185.88.181.60/ 185.88.181.60 http://www.xvideos.com/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch X Fatal error: Nameserver doesn't support TCP connection: ns1.xxx.org / 69.55.53.49: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.xxx.org / 69.55.57.70: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns3.xxx.org / 141.0.168.100: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns4.xxx.org / 141.0.172.32: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns5.xxx.org / 141.0.168.79: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns6.xxx.org / 141.0.173.184: Timeout 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 www.xnxx.com, 8 ip addresses. 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 xnxx.com, 8 ip addresses. Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.xnxx.com, 8 ip addresses, 1 different http results. Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain xnxx.com, 8 ip addresses, 1 different http results. 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.xnxx.com 2. Header-Checks A www.xnxx.com 185.88.181.53 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A www.xnxx.com 185.88.181.54 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A www.xnxx.com 185.88.181.55 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A www.xnxx.com 185.88.181.56 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A www.xnxx.com 185.88.181.57 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A www.xnxx.com 185.88.181.58 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A www.xnxx.com 185.88.181.59 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. A www.xnxx.com 185.88.181.60 Content-Security-Policy Ok: Header without syntax errors found: default-src 'self' data: 'unsafe-inline' 'unsafe-eval' blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com 1868565294.rsc.cdn77.org *.trafficfactory.biz www.iwanttodeliver.com www.google.com www.gstatic.com fonts.gstatic.com fonts.googleapis.com ajax.googleapis.com fcm.googleapis.com accounts.google.com *.cdn77.org *.nk-img.com *.segpay.com *.online-metrix.net *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net *.adglare.net www.flirt4free.com www.ohmybutt.com www.secretpartners.com cdn.asf4f.us *.livejasmin.com *.jsmcrptjmp.com *.awemwh.com etahub.com ctrack.trafficjunky.net tracking.sexcash.com *.gtflixtv.com;img-src 'self' 'unsafe-inline' data: blob: *.xvideos.com *.xnxx.com *.red-cdn.com *.gold-cdn.com *.xvideos-cdn.com *.xnxx-cdn.com *.others-cdn.com *.cdn77.org *.trafficfactory.biz www.google.com www.google-analytics.com ssl.gstatic.com *.nk-img.com *.camster.com *.vscdns.com *.doubleclick.net *.google.fr *.google.com *.segpay.com *.online-metrix.net *.gtflixtv.com *.exoclick.com *.exosrv.com *.realsrv.com *.orbsrv.com *.exdynsrv.com *.ackcdn.net *.afcdn.net *.aucdn.net bmedia.justservingfiles.net *.tf4srv.com *.aacdn.net; F Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition. F Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it. 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. E Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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. E Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources. E Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted. F Dangerous: No script-src defined, but the default-src as fallback allows the data: schema. That allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens. F Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens. A Referrer-Policy Ok: Header without syntax errors found: no-referrer-when-downgrade A X-Frame-Options Ok: Header without syntax errors found: SAMEORIGIN B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls. F www.xnxx.com 185.88.181.53 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.53 Permissions-Policy Critical: Missing Header: F www.xnxx.com 185.88.181.54 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.54 Permissions-Policy Critical: Missing Header: F www.xnxx.com 185.88.181.55 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.55 Permissions-Policy Critical: Missing Header: F www.xnxx.com 185.88.181.56 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.56 Permissions-Policy Critical: Missing Header: F www.xnxx.com 185.88.181.57 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.57 Permissions-Policy Critical: Missing Header: F www.xnxx.com 185.88.181.58 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.58 Permissions-Policy Critical: Missing Header: F www.xnxx.com 185.88.181.59 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.59 Permissions-Policy Critical: Missing Header: F www.xnxx.com 185.88.181.60 X-Content-Type-Options Critical: Missing Header: F www.xnxx.com 185.88.181.60 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers. A Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. A Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.xxx.org (69.55.53.49), ns2.xxx.org (69.55.57.70), ns3.xxx.org (141.0.168.100), ns4.xxx.org (141.0.172.32), ns5.xxx.org (141.0.168.79), ns6.xxx.org (141.0.173.184) A Good (1 - 3.0):: An average of 0.3 queries per domain name server required to find all ip addresses of all name servers. A Info:: 6 different Name Servers found: ns1.xxx.org, ns2.xxx.org, ns3.xxx.org, ns4.xxx.org, ns5.xxx.org, ns6.xxx.org, 6 Name Servers included in Delegation: ns1.xxx.org, ns2.xxx.org, ns3.xxx.org, ns4.xxx.org, ns5.xxx.org, ns6.xxx.org, 6 Name Servers included in 1 Zone definitions: ns1.xxx.org, ns2.xxx.org, ns3.xxx.org, ns4.xxx.org, ns5.xxx.org, ns6.xxx.org, 1 Name Servers listed in SOA.Primary: ns1.xxx.org. A Good: Only one SOA.Primary Name Server found.: ns1.xxx.org. A Good: SOA.Primary Name Server included in the delegation set.: ns1.xxx.org. A Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.xxx.org, ns2.xxx.org, ns3.xxx.org, ns4.xxx.org, ns5.xxx.org, ns6.xxx.org 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: 6 different Name Servers found Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 6 different Name Servers found Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 6 Name Servers, 1 Top Level Domain: org 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: xxx.org Warning: All Name Servers from the same Country / IP location.: 6 Name Servers, 1 Countries: NL A Info: Ipv4-Subnet-list: 6 Name Servers, 2 different subnets (first Byte): 141., 69., 2 different subnets (first two Bytes): 141.0., 69.55., 5 different subnets (first three Bytes): 141.0.168., 141.0.172., 141.0.173., 69.55.53., 69.55.57. A Good: Name Server IPv4-addresses from different subnet found: A Good: Nameserver supports Echo Capitalization: 6 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver A Good: All SOA have the same Serial Number Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries. 4. Content- and Performance-critical Checks 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 Good: Every https result with status 200 supports GZip. https://www.xnxx.com/ 185.88.181.53 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.54 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.55 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.56 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.57 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.58 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.59 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.60 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xvideos.com/ Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://www.xnxx.com/ 185.88.181.53 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xnxx.com/ 185.88.181.54 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xnxx.com/ 185.88.181.55 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xnxx.com/ 185.88.181.56 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xnxx.com/ 185.88.181.57 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xnxx.com/ 185.88.181.58 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xnxx.com/ 185.88.181.59 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xnxx.com/ 185.88.181.60 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://www.xvideos.com/ Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. A 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: 765573 milliseconds, 765.573 seconds