Zapier
Connects thousands of web apps with no-code triggers and actions, so an event in one app can create, update or send something in another.
Compare
Security headers: B, 80 out of 100
Number 33 of 95 in the ranking. Missing 3 of the 9 headers we check.
Meets the B minimum (70/100) in our RFP clause.
With these headers missing, zapier.com is more exposed to clickjacking.
Missing 3
-
Permissions-Policy 0 of 10
Switches off browser features the product does not use, such as camera, microphone, location and payments, for the page and anything embedded in it.
Without it: Any script or iframe on the page, including third-party ads and chat widgets, can ask the user for camera, microphone or location access under the vendor's name.
-
Cross-Origin-Opener-Policy 0 of 5
Cuts the link between the product's window and windows opened by, or opening, other sites.
Without it: A page that opens the product keeps a handle on its window and can later redirect it to a look-alike sign-in or payment page (tab-nabbing) while the user thinks they are still on the real site. It is also part of the isolation browsers need to defend against Spectre-style attacks.
-
Cross-Origin-Resource-Policy 0 of 5
Tells browsers which sites may load this site's resources.
Without it: Other sites can pull the product's responses into their own pages, which makes side-channel leaks of what a signed-in user can see easier.
Sent 6
-
Content-Security-Policy 25 of 25
frame-ancestors 'self' https://app.contentful.com;
-
Strict-Transport-Security 20 of 20
max-age=31536000; includeSubDomains; preload
-
X-Content-Type-Options 10 of 10
nosniff
-
Frame protection 10 of 10
CSP frame-ancestors
-
Referrer-Policy 10 of 10
strict-origin-when-cross-origin
-
No version disclosure 5 of 5
server: Vercel