All-in-one free web application security tool. Web application vulnerability and privacy scanner with support for HTTP cookies, Flash, HTML5 localStorage, sessionStorage, CANVAS, Supercookies, Evercookies. Includes a free SSL/TLS, HTML and HTTP vulnerability scanner and URL malware scanner.
Category: Videos Video Streaming
Keywords: high vimeo errors human: number pardon verify blocked servers continue detected forbidden connection temporarily inconvenience
Last fetched: 2020-02-26T10:21:44.210145+00:00
HTTP status: 5 Sub-resource URL
Server: nginx
Announces web server software and optionally version details.
Read more...X-XSS-Protection: 1; mode=block
Controls an Cross-Site Scripting (XSS) filters built into the majority of web browsers. The filter is usually turned on by default anyway, but requirement to set the header to 1
became part of canonical set of "secure" HTTP headers. Over time, vulnerabilities in the "sanitizing" mode filter were found, so 1; mode=block
became the recommended value. Some companies decided that they don't really need a browser-side XSS filter to mess with their web services which are XSS-free anyway and they became consciously disabling the XSS filter by setting the header to 0
.
XSS auditor is enabled in blocking mode
+1X-Content-Type-Options: nosniff
A non-standard but widely accepted header introduced originally by Microsoft to disable "content sniffing" or heuristic content type discovery in absence or mismatch of a proper HTTP Content-Type
declaration, which led to a number of web attacks. In general, presence of the header with its only defined value of nosniff
is considered as part of a properly secured HTTP response.
Fuzzy content type guessing is disabled
+1Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header.
Read more...
HTTP Strict Transport Security is enabled
+2Link: <https://i.vimeocdn.com>; rel=preconnect; crossorigin
Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.
Read more...
The HTML5 Resource hint is a relatively new web performance feature that hints the browser that it might make sense to fetch the specified resource even before page rendering has been even finished as it may be needed next.
0Link: <https://f.vimeocdn.com>; rel=preconnect; crossorigin
Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.
Read more...
The HTML5 Resource hint is a relatively new web performance feature that hints the browser that it might make sense to fetch the specified resource even before page rendering has been even finished as it may be needed next.
0Link: <https://fresnel.vimeocdn.com>; rel=preconnect; crossorigin
Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.
Read more...
The HTML5 Resource hint is a relatively new web performance feature that hints the browser that it might make sense to fetch the specified resource even before page rendering has been even finished as it may be needed next.
0P3P: CP="This is not a P3P policy! See https://vimeo.com/privacy"
Largely abandoned format for declaring website's privacy policy in machine-readable format. The only reason for many websites to use the header was that old versions of Microsoft Internet Explorer disallowed third-party cookies on websites missing P3P.
Read more...
P3P is a mostly abandoned standard for website privacy policy declaration that has little use today. Please consider switching to DoNotTrack standard.
0Transport Layer Security (TLS) is enabled
+2X-Frame-Options
header is missing
script-src 'self' 'unsafe-inline' blob: resource: https://f.vimeocdn.com https://vimeo.com https://js-agent.newrelic.com https://imasdk.googleapis.com/ https://adservice.google.com/ https://s0.2mdn.net/instream/video/ https://bam.nr-data.net https://src.litix.io https://www.gstatic.com https://cdn.streamroot.io https://f.vimeocdn.com; style-src 'self' 'unsafe-inline' https://f.vimeocdn.com https://f.vimeocdn.com; connect-src 'self' ws: wss: https://vimeo.com https://vimeo.dev https://api.vimeo.com https://api.vimeo.dev https://*.ci.vimeows.com https://csi.gstatic.com https://fresnel.vimeocdn.com https://*.akamaized.net https://*.akamaized-staging.net https://*.vimeocdn.com https://netflux.cloud.vimeo.com https://lic.staging.drmtoday.com https://lic.drmtoday.com https://wv.service.expressplay.com https://fp.service.expressplay.com https://pr.service.expressplay.com https://sentry.io https://storage.googleapis.com https://bam.nr-data.net https://live-api.cloud.vimeo.com https://live-api-dev.cloud.vimeo.com https://*.litix.io/ https://collector.vhx.tv https://collector.vhxstaging.com https://backend.dna-delivery.com https://mimir.cloud.vimeo.com; media-src 'self' blob: https://*.vimeocdn.com https://*.akamaized.net https://*.akamaized-staging.net https://*.gvt1.com https://live-api.cloud.vimeo.com https://live-api-dev.cloud.vimeo.com; object-src 'self' https://*.vimeocdn.com https://*.akamaized.net https://*.akamaized-staging.net; default-src 'none'; img-src 'self' data: https://i.vimeocdn.com https://secure-b.vimeocdn.com https://f.vimeocdn.com https://vimeo.com https://secure.gravatar.com https://i0.wp.com https://i1.wp.com https://i2.wp.com https://pagead2.googlesyndication.com https://player.vimeo.com https://*.ci.vimeows.com https://f.vimeocdn.com; frame-src 'self' https://imasdk.googleapis.com/ https://f.vimeocdn.com
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src https://www.gstatic.com
is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Want second opinion? Try Google CSP Evaluator.