1. General Results, most used to calculate the result A name "yahoo.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.yahoo.com has 4 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: yahoo.com has 22 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: www.yahoo.com has 2 ipv4, 2 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: yahoo.com has 16 ipv4, 6 ipv6 addresses A Good: No asked Authoritative Name Server had a timeout A Good: one preferred version: www is preferred A Good: No cookie sent via http. 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):9 complete Content-Type - header (31 urls) http://www.yahoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.248.100.215 Url with incomplete Content-Type - header - missing charset http://www.yahoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.248.100.216 Url with incomplete Content-Type - header - missing charset http://www.yahoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1288:110:c305::1:8000 Url with incomplete Content-Type - header - missing charset http://www.yahoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1288:110:c305::1:8001 Url with incomplete Content-Type - header - missing charset https://34.225.127.72/ 34.225.127.72 Url with incomplete Content-Type - header - missing charset https://54.161.105.65/ 54.161.105.65 Url with incomplete Content-Type - header - missing charset https://74.6.143.25/ 74.6.143.25 Url with incomplete Content-Type - header - missing charset https://74.6.143.26/ 74.6.143.26 Url with incomplete Content-Type - header - missing charset https://74.6.231.20/ 74.6.231.20 Url with incomplete Content-Type - header - missing charset https://74.6.231.21/ 74.6.231.21 Url with incomplete Content-Type - header - missing charset https://98.137.11.163/ 98.137.11.163 Url with incomplete Content-Type - header - missing charset https://98.137.11.164/ 98.137.11.164 Url with incomplete Content-Type - header - missing charset https://[2001:4998:0024:120d:0000:0000:0001:0000]/ 2001:4998:24:120d::1:0 Url with incomplete Content-Type - header - missing charset https://[2001:4998:0024:120d:0000:0000:0001:0001]/ 2001:4998:24:120d::1:1 Url with incomplete Content-Type - header - missing charset https://[2001:4998:0044:3507:0000:0000:0000:8000]/ 2001:4998:44:3507::8000 Url with incomplete Content-Type - header - missing charset https://[2001:4998:0044:3507:0000:0000:0000:8001]/ 2001:4998:44:3507::8001 Url with incomplete Content-Type - header - missing charset https://[2001:4998:0124:1507:0000:0000:0000:f000]/ 2001:4998:124:1507::f000 Url with incomplete Content-Type - header - missing charset https://[2001:4998:0124:1507:0000:0000:0000:f001]/ 2001:4998:124:1507::f001 Url with incomplete Content-Type - header - missing charset https://87.248.100.215/ 87.248.100.215 Url with incomplete Content-Type - header - missing charset https://87.248.100.216/ 87.248.100.216 Url with incomplete Content-Type - header - missing charset https://[2a00:1288:0110:c305:0000:0000:0001:8000]/ 2a00:1288:110:c305::1:8000 Url with incomplete Content-Type - header - missing charset https://[2a00:1288:0110:c305:0000:0000:0001:8001]/ 2a00:1288:110:c305::1:8001 Url with incomplete Content-Type - header - missing charset C http://www.yahoo.com/ 87.248.100.215 http://www.yahoo.com Error - redirect destination with a missing / at the end found. So two http status 200 results, only difference: An ending /. Perhaps missing "/" in the redirect rule. May be a problem redirecting folders and files. C http://www.yahoo.com/ 87.248.100.216 http://www.yahoo.com Error - redirect destination with a missing / at the end found. So two http status 200 results, only difference: An ending /. Perhaps missing "/" in the redirect rule. May be a problem redirecting folders and files. C http://www.yahoo.com/ 2a00:1288:110:c305::1:8000 http://www.yahoo.com Error - redirect destination with a missing / at the end found. So two http status 200 results, only difference: An ending /. Perhaps missing "/" in the redirect rule. May be a problem redirecting folders and files. C http://www.yahoo.com/ 2a00:1288:110:c305::1:8001 http://www.yahoo.com Error - redirect destination with a missing / at the end found. So two http status 200 results, only difference: An ending /. Perhaps missing "/" in the redirect rule. May be a problem redirecting folders and files. D http://yahoo.com/ 34.225.127.72 http://www.yahoo.com 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://yahoo.com/ 54.161.105.65 http://www.yahoo.com 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://yahoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.225.127.72 http://www.yahoo.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://yahoo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 54.161.105.65 http://www.yahoo.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://yahoo.com/ 74.6.143.25 https://www.yahoo.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://yahoo.com/ 74.6.143.26 https://www.yahoo.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://yahoo.com/ 74.6.231.20 https://www.yahoo.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://yahoo.com/ 74.6.231.21 https://www.yahoo.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://yahoo.com/ 98.137.11.163 https://www.yahoo.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://yahoo.com/ 98.137.11.164 https://www.yahoo.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://yahoo.com/ 2001:4998:24:120d::1:0 https://www.yahoo.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://yahoo.com/ 2001:4998:24:120d::1:1 https://www.yahoo.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://yahoo.com/ 2001:4998:44:3507::8000 https://www.yahoo.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://yahoo.com/ 2001:4998:44:3507::8001 https://www.yahoo.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://yahoo.com/ 2001:4998:124:1507::f000 https://www.yahoo.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://yahoo.com/ 2001:4998:124:1507::f001 https://www.yahoo.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://yahoo.com/ 34.225.127.72 http://www.yahoo.com Wrong redirect https - http - never redirect https to http F https://yahoo.com/ 54.161.105.65 http://www.yahoo.com Wrong redirect https - http - never redirect https to http H Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. M https://34.225.127.72/ 34.225.127.72 Misconfiguration - main pages should never send http status 400 - 499 M https://54.161.105.65/ 54.161.105.65 Misconfiguration - main pages should never send http status 400 - 499 M https://74.6.143.25/ 74.6.143.25 Misconfiguration - main pages should never send http status 400 - 499 M https://74.6.143.26/ 74.6.143.26 Misconfiguration - main pages should never send http status 400 - 499 M https://74.6.231.20/ 74.6.231.20 Misconfiguration - main pages should never send http status 400 - 499 M https://74.6.231.21/ 74.6.231.21 Misconfiguration - main pages should never send http status 400 - 499 M https://98.137.11.163/ 98.137.11.163 Misconfiguration - main pages should never send http status 400 - 499 M https://98.137.11.164/ 98.137.11.164 Misconfiguration - main pages should never send http status 400 - 499 M https://[2001:4998:0024:120d:0000:0000:0001:0000]/ 2001:4998:24:120d::1:0 Misconfiguration - main pages should never send http status 400 - 499 M https://[2001:4998:0024:120d:0000:0000:0001:0001]/ 2001:4998:24:120d::1:1 Misconfiguration - main pages should never send http status 400 - 499 M https://[2001:4998:0044:3507:0000:0000:0000:8000]/ 2001:4998:44:3507::8000 Misconfiguration - main pages should never send http status 400 - 499 M https://[2001:4998:0044:3507:0000:0000:0000:8001]/ 2001:4998:44:3507::8001 Misconfiguration - main pages should never send http status 400 - 499 M https://[2001:4998:0124:1507:0000:0000:0000:f000]/ 2001:4998:124:1507::f000 Misconfiguration - main pages should never send http status 400 - 499 M https://[2001:4998:0124:1507:0000:0000:0000:f001]/ 2001:4998:124:1507::f001 Misconfiguration - main pages should never send http status 400 - 499 M https://87.248.100.215/ 87.248.100.215 Misconfiguration - main pages should never send http status 400 - 499 M https://87.248.100.216/ 87.248.100.216 Misconfiguration - main pages should never send http status 400 - 499 M https://[2a00:1288:0110:c305:0000:0000:0001:8000]/ 2a00:1288:110:c305::1:8000 Misconfiguration - main pages should never send http status 400 - 499 M https://[2a00:1288:0110:c305:0000:0000:0001:8001]/ 2a00:1288:110:c305::1:8001 Misconfiguration - main pages should never send http status 400 - 499 N https://34.225.127.72/ 34.225.127.72 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://54.161.105.65/ 54.161.105.65 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://74.6.143.25/ 74.6.143.25 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://74.6.143.26/ 74.6.143.26 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://74.6.231.20/ 74.6.231.20 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://74.6.231.21/ 74.6.231.21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://98.137.11.163/ 98.137.11.163 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://98.137.11.164/ 98.137.11.164 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2001:4998:0024:120d:0000:0000:0001:0000]/ 2001:4998:24:120d::1:0 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2001:4998:0024:120d:0000:0000:0001:0001]/ 2001:4998:24:120d::1:1 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2001:4998:0044:3507:0000:0000:0000:8000]/ 2001:4998:44:3507::8000 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2001:4998:0044:3507:0000:0000:0000:8001]/ 2001:4998:44:3507::8001 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2001:4998:0124:1507:0000:0000:0000:f000]/ 2001:4998:124:1507::f000 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2001:4998:0124:1507:0000:0000:0000:f001]/ 2001:4998:124:1507::f001 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://87.248.100.215/ 87.248.100.215 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://87.248.100.216/ 87.248.100.216 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2a00:1288:0110:c305:0000:0000:0001:8000]/ 2a00:1288:110:c305::1:8000 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2a00:1288:0110:c305:0000:0000:0001:8001]/ 2a00:1288:110:c305::1:8001 Error - Certificate isn't trusted, RemoteCertificateNameMismatch 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.yahoo.com, 4 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 yahoo.com, 14 ip addresses. Warning: More then one ip address per domain name found, checking all ip addresses the same http status, but different certificates found: Domain www.yahoo.com, 4 ip addresses, 2 certificates. Warning: More then one ip address per domain name found, checking all ip addresses the same http status, but different certificates found: Domain yahoo.com, 14 ip addresses, 2 certificates. 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.yahoo.com, 4 ip addresses, 1 different http results. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain yahoo.com, 14 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.yahoo.com 2. Header-Checks A www.yahoo.com 87.248.100.215 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com; sandbox allow-forms allow-same-origin allow-scripts allow-popups allow-popups-to-escape-sandbox allow-presentation; report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=6d7qoodighbq0&partner=; B Info: Header-Element is deprecated. report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=6d7qoodighbq0&partner= E Critical: Duplicated entries found frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com
Duplicated entries: https://*.autoblog.com 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 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 X-Xss-Protection Ok: Header without syntax errors found: 1; mode=block B Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block A www.yahoo.com 87.248.100.216 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com; sandbox allow-forms allow-same-origin allow-scripts allow-popups allow-popups-to-escape-sandbox allow-presentation; report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=6m47f0highbq7&partner=; B Info: Header-Element is deprecated. report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=6m47f0highbq7&partner= E Critical: Duplicated entries found frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com
Duplicated entries: https://*.autoblog.com 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 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 X-Xss-Protection Ok: Header without syntax errors found: 1; mode=block B Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block A www.yahoo.com 2a00:1288:110:c305::1:8000 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com; sandbox allow-forms allow-same-origin allow-scripts allow-popups allow-popups-to-escape-sandbox allow-presentation; report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=40ffa2tighbqd&partner=; B Info: Header-Element is deprecated. report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=40ffa2tighbqd&partner= E Critical: Duplicated entries found frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com
Duplicated entries: https://*.autoblog.com 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 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 X-Xss-Protection Ok: Header without syntax errors found: 1; mode=block B Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block A www.yahoo.com 2a00:1288:110:c305::1:8001 Content-Security-Policy Ok: Header without syntax errors found: frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com; sandbox allow-forms allow-same-origin allow-scripts allow-popups allow-popups-to-escape-sandbox allow-presentation; report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=3pnp4kpighbqk&partner=; B Info: Header-Element is deprecated. report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage®ion=US&lang=en-US&device=desktop&yrid=3pnp4kpighbqk&partner= E Critical: Duplicated entries found frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com
Duplicated entries: https://*.autoblog.com 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 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 X-Xss-Protection Ok: Header without syntax errors found: 1; mode=block B Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block F www.yahoo.com 87.248.100.215 Permissions-Policy Critical: Missing Header: F www.yahoo.com 87.248.100.216 Permissions-Policy Critical: Missing Header: F www.yahoo.com 2a00:1288:110:c305::1:8000 Permissions-Policy Critical: Missing Header: F www.yahoo.com 2a00:1288:110:c305::1:8001 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 5 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.yahoo.com (2001:4998:1b0::7961:686f:6f21, 68.180.131.16), ns2.yahoo.com (2001:4998:1c0::7961:686f:6f21, 68.142.255.16), ns3.yahoo.com (2406:8600:f03f:1f8::1003, 27.123.42.42), ns4.yahoo.com (98.138.11.157), ns5.yahoo.com (202.165.97.53, 2406:2000:1d0::7961:686f:6f21) A Good (1 - 3.0):: An average of 0.4 queries per domain name server required to find all ip addresses of all name servers. A Info:: 5 different Name Servers found: ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com, 5 Name Servers included in Delegation: ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com, 5 Name Servers included in 1 Zone definitions: ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com, 1 Name Servers listed in SOA.Primary: ns1.yahoo.com. A Good: Only one SOA.Primary Name Server found.: ns1.yahoo.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1.yahoo.com. 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.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com A Good: All Name Server Domain Names have a Public Suffix. A Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address. A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 5 different Name Servers found A Good: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (1 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.: 5 Name Servers, 1 Top Level Domain: com 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: yahoo.com A Good: Name servers with different Country locations found: 5 Name Servers, 5 Countries: AU, IN, SG, TW, US A Info: Ipv4-Subnet-list: 5 Name Servers, 4 different subnets (first Byte): 202., 27., 68., 98., 5 different subnets (first two Bytes): 202.165., 27.123., 68.142., 68.180., 98.138., 5 different subnets (first three Bytes): 202.165.97., 27.123.42., 68.142.255., 68.180.131., 98.138.11. 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): 2001:, 2406:, 3 different subnets (first two blocks): 2001:4998:, 2406:2000:, 2406:8600:, 4 different subnets (first three blocks): 2001:4998:01b0:, 2001:4998:01c0:, 2406:2000:01d0:, 2406:8600:f03f:, 4 different subnets (first four blocks): 2001:4998:01b0:0000:, 2001:4998:01c0:0000:, 2406:2000:01d0:0000:, 2406:8600:f03f:01f8: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 18 good Nameserver A Good: Nameserver supports Echo Capitalization: 18 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 18 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 18 good Nameserver A Good: All SOA have the same Serial Number A Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates A Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates 4. Content- and Performance-critical Checks A Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://www.yahoo.com/ 87.248.100.215 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.yahoo.com/ 87.248.100.216 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.yahoo.com/ 2a00:1288:110:c305::1:8000 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.yahoo.com/ 2a00:1288:110:c305::1:8001 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. A Good: Every https connection via port 443 supports the http/2 protocol via ALPN. A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 4 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 4 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 4 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: All img-elements have a valid alt-attribute.: 4 img-elements found. A Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx http://www.yahoo.com Warning: HSTS header sent via http has no effect http://www.yahoo.com/ 87.248.100.215 Warning: HSTS header sent via http has no effect http://www.yahoo.com/ 87.248.100.216 Warning: HSTS header sent via http has no effect http://www.yahoo.com/ 2a00:1288:110:c305::1:8000 Warning: HSTS header sent via http has no effect http://www.yahoo.com/ 2a00:1288:110:c305::1:8001 Warning: HSTS header sent via http has no effect https://34.225.127.72/ 34.225.127.72 9.377 seconds Warning: 404 needs more then one second https://54.161.105.65/ 54.161.105.65 4.633 seconds Warning: 404 needs more then one second https://74.6.143.25/ 74.6.143.25 4.380 seconds Warning: 404 needs more then one second https://74.6.143.26/ 74.6.143.26 4.360 seconds Warning: 404 needs more then one second https://74.6.231.20/ 74.6.231.20 4.930 seconds Warning: 404 needs more then one second https://74.6.231.21/ 74.6.231.21 4.914 seconds Warning: 404 needs more then one second https://98.137.11.163/ 98.137.11.163 5.646 seconds Warning: 404 needs more then one second https://98.137.11.164/ 98.137.11.164 5.620 seconds Warning: 404 needs more then one second https://[2001:4998:0024:120d:0000:0000:0001:0000]/ 2001:4998:24:120d::1:0 5.527 seconds Warning: 404 needs more then one second https://[2001:4998:0024:120d:0000:0000:0001:0001]/ 2001:4998:24:120d::1:1 5.473 seconds Warning: 404 needs more then one second https://[2001:4998:0044:3507:0000:0000:0000:8000]/ 2001:4998:44:3507::8000 4.860 seconds Warning: 404 needs more then one second https://[2001:4998:0044:3507:0000:0000:0000:8001]/ 2001:4998:44:3507::8001 4.850 seconds Warning: 404 needs more then one second https://[2001:4998:0124:1507:0000:0000:0000:f000]/ 2001:4998:124:1507::f000 4.277 seconds Warning: 404 needs more then one second https://[2001:4998:0124:1507:0000:0000:0000:f001]/ 2001:4998:124:1507::f001 4.300 seconds Warning: 404 needs more then one second https://87.248.100.215/ 87.248.100.215 3.040 seconds Warning: 404 needs more then one second https://87.248.100.216/ 87.248.100.216 3.070 seconds Warning: 404 needs more then one second https://[2a00:1288:0110:c305:0000:0000:0001:8000]/ 2a00:1288:110:c305::1:8000 3.040 seconds Warning: 404 needs more then one second https://[2a00:1288:0110:c305:0000:0000:0001:8001]/ 2a00:1288:110:c305::1:8001 3.094 seconds Warning: 404 needs more then one second A Duration: 465490 milliseconds, 465.490 seconds