Dear Webflow team,

In Europe, the NIS2 directive places strong emphasis on cybersecurity. To comply, many companies are required to implement strict security measures — including proper security headers — even at lower-tier service levels.

Without these features available by default, European customers may no longer be able to choose Webflow as a compliant partner under the NIS2 framework.

Are there any plans to make essential security headers available across all tiers?

Here to pile on sentiments that my non-Enterprise site should be able to pass securityheaders.com/penetration testing without routing through Cloudflare. 🥺

While I appreciate the recent addition of HSTS, we still need to add X-Content-Type-Options (Why no toggle for nosniff under Advanced publishing options while you were already breaking out subdomains and preload?), Referrer-Policy and Permissions-Policy security headers.

Speaking of which, why does Webflow still prioritize the outdated Features-Policy? 🤔

Security Headers should not be a enterprise only features in my eyes. Since most of them can be set for our Wordpress client with a couple of lines inside a htaccess file.

Hi all, we just redesigned our site and moved it over to Webflow, only to find out that we are on Core and can't add custom security headers. This a HUGE problem for us. Will this be available to all customers soon or is there a manual workaround that we can implement?

Unbelievable that security settings/headers are only available to Enterprise customers. Thinking about using cloudflare or the like to fix this. Any suggestions?

We have recently moved to Webflow, reading the guides and working with the agency before we agreed to move, we believed Security Headers would be available.

Since moving over to Webflow we have now found that they are only available to Enterprise customers.

Can security headers please be made available to all paid plans?

Fundamental Security MUST be a standard offering for all users of any service NOT just Enterprise customers.

A financial institution partner is running an audit on our webflow landing pages and found that the default security headers are insufficient.

They keep insisting we upgrade; however, we're stuck because custom security headers is only available to Webflow Enterprise customers.

This is becoming a dealbreaker for us - can we please get support for this feature?

THIS should be a MUST HAVE in no matter which option and not just in ENTERPRISE!!!! Especially in EU countries. Otherwise many freelancers and web agencies are going to have HUUUUUUUUGE problems with GDPR. If this doesn't become a default feature, many EU-people gotta stop working with Webflow. And that would be really sad.

Why can't they just release a simple security pack for an extra $3 a month? Otherwise just give it standard. If a Google check says this is a security risk it should be addressed. Small organisations can't afford Enterprise Lite.

This definitely seems like a basic option that should be at least be available in the Business option.

I believe that this is available in Enterprise Lite now, right?

You can host the Site with Stacket: https://stacket.app/ where you want, and then add the security headers what you prefer :)

This has been the deal breaker on many projects, and it's pretty much the same scenario.

It's an easy sell to creatives and account people when all they can see are the visual aspects of Webflow, great content editing and layout tools. But when we start talking hosting and infosec related matters, it's a deal breaker.

Not having this means we need to introduce new tooling to get around this issue, either by creating proxy servers or custom pipeline scripts to handle the exporting and rebuilding of site with dynamic content.

There ways to work around this, but it's annoying, costly and fragile. So the result is just referring them to another tool or process.

Hey, this is becoming a bit of a problem. Can we please have the ability to put our own headers on our website? If not add some standards in there such as

• X-Content-Type-Options

• Strict-Transport-Security

• Referrer-Policy

• Permissions-Policy

Thanks

Adding X-Content-Type-Options: nosniff should be a trivial change

This seems an obvious target to implement - but doing so in such a way that limits the self harm that can come from incorrect set-up is the real deal right? I have financial sector clients (non transactional sites & marketing) that I can't realistically use for Webflow because a simple scan of the headers (even of webflow.com !) shows a poor 'D' rating.

Curiously, the security rating that Webflow sites score for their headers varies. When you look at the enterprise showcase sites of HelloSign and Brandland.Zendesk they receive a D and an F respectively. The Zendesk site has no CSP or X-Frame options set, whereas HelloSign at least has those 2.

Which begs the question? Did the Zendesk site happen before these became a core part of Webflow or did one of these two clients get some customisation aspect?

Either way - some beefing up of the offering here would go a long way to meeting the basic expectations of more larger clients.

Need this as well! Any updates?

Yes! Also need this - has anyone been able to achieve this?

Please, please please, we need this implemented. This is the final key to making webflow a 100% fast, secure web host, it's a no-brainer.

Curious to know if any of you have been successful with Webflow's team to get this addressed.