Beta: the full scanner is free while it is in beta. Sign in and scan a site

ScanBastion Start Free Beta Scan

Learn

Webflow security assessment for clients: what you can and cannot control

On a Webflow site, Webflow runs the servers, the TLS certificates and the patching. The useful work is in the parts the agency and the client control: custom code, third-party scripts, forms, published files, the plan's header settings and the client's DNS. This guide separates what you can change from what you can only report, and ends with what to put in the client report.

Webflow's features change by plan, so check the client's current plan against Webflow's help pages before you promise a fix. As with any assessment, get the client's written authorisation first; see how DNS TXT verification works.

1. What Webflow controls, by plan

  • TLS. SSL is on for every site and cannot be disabled. Certificates renew automatically while the DNS records point to Webflow. Uploading your own certificate is an Enterprise feature.
  • HSTS. On non-Enterprise sites Webflow turns HSTS on automatically and it cannot be disabled; HSTS with subdomains and preload can be switched on in Site settings, Publishing, Advanced publishing options. Check what the live site sends before reporting an HSTS issue.
  • Framing. The "Use secure frame headers" option adds headers that stop other sites embedding the pages. It cannot be turned off on sites with Ecommerce or User Accounts. If a scan reports clickjacking on a Webflow site, this option is usually off.
  • Other security headers (Content-Security-Policy, Referrer-Policy, X-Content-Type-Options and others) can be set only as custom security headers, which are available to Enterprise customers and unlocked per site by Webflow's sales team. Webflow does not support Permissions-Policy at all, and its support team does not help configure these headers.

So on most client plans, a missing CSP, Referrer-Policy or Permissions-Policy cannot be fixed in Webflow. The honest options are to accept and document it, to move to Enterprise, or to put Cloudflare in front of the site with Webflow's supported Orange-to-Orange set-up and add headers there. Cloudflare lists Transform Rules as compatible with that set-up, with a warning that rules matching the hostname can interfere with traffic, and Webflow does not support third-party configuration, so test on a non-critical hostname first.

2. Custom code and third-party scripts

This is where most real risk on a Webflow site sits. Sites with a paid Site plan, or in a Core, Growth, Agency or Freelancer Workspace, can add code in Site settings (head and footer), in each page's settings and in Code Embed elements, including inside CMS rich text.

  • Inventory every script: what it does, who owns the account behind it, and whether it is still used. Abandoned chat widgets and a former agency's tag manager are common finds.
  • Subresource Integrity. Webflow serves its jQuery copy and the site's own scripts and stylesheet with integrity attributes, so most "third-party script without Subresource Integrity" findings on a Webflow site point at custom code. Not all: files Webflow adds for some features, such as the Google Fonts loader or GSAP, can arrive without one. Check the host and path before you assign the finding. Pin a version and add integrity where the provider publishes fixed files; tag managers and analytics loaders cannot carry a fixed hash, and are a decision to record rather than a fix.
  • Libraries. Webflow sites published since August 2020 load jQuery 3.5.1; a second jQuery or an old slider library added through custom code is both a conflict and an outdated-component finding.
  • Ecommerce. Webflow points out that scripts you add are outside its control and may affect your PCI DSS obligations. On a store, every script on checkout pages needs a named owner.

3. Forms, files and staging

  • Forms. Check where each form submits (Webflow, an integration or a custom action URL), that the action is HTTPS, who receives the notification emails, and that spam protection is on: reCAPTCHA, the Cloudflare Turnstile bot-blocking setting, or a honeypot field.
  • Uploaded files are public. Files in the Assets panel or a CMS field are served from Webflow's CDN to anyone with the URL, whether or not a page links to them. Look for contracts, price lists and internal PDFs; Webflow can remove a file from its CDN on request. Password protection on a page stops its links being discovered, not the file being fetched.
  • The staging domain. yoursite.webflow.io is public unless you act. Disable search indexing for it, and check it does not show unreleased pages or prices.

4. DNS and email on the client's domain

The domain is the client's, and so are its weaknesses. ScanBastion's DNS and email checks run in every profile: SPF, DMARC, DKIM at common selectors, CAA, and dangling CNAMEs.

  • SPF and DMARC. A marketing site that sends no mail still needs v=spf1 -all and a DMARC policy, or anyone can send convincing mail from it.
  • CAA. A CAA record is good practice, but on Webflow it must allow Webflow's certificate providers, or certificates stop provisioning and renewing. Follow Webflow's CAA instructions before you add one.
  • Leftover CNAMEs. ScanBastion checks the scanned host, its www variant and the bare domain for CNAMEs whose target no longer resolves, and treats a dead *.webflow.io target as a likely takeover. A stale CNAME to cdn.webflow.com still resolves, so it is not flagged. Compare every subdomain in the zone with the domains listed in each Webflow project's publishing settings, and remove records for campaigns that ended.

5. Cookie banners and consent

No scanner can tell whether a consent banner is lawful. Open the site in a fresh browser profile, refuse consent, and check in the developer tools which cookies are set and which third-party requests still go out. ScanBastion sees cookies only in Set-Cookie headers, so cookies written by JavaScript, which is how most tracking tags set them, do not appear in its findings.

6. What to put in the client report

  • Scope: the site is hosted on Webflow, on a named plan; the platform's own infrastructure was not assessed.
  • Findings in three groups: fixable now in Webflow (framing option, custom code, forms, assets, staging), fixable with a plan change or Cloudflare (CSP and other headers), and accepted platform limits (Permissions-Policy), each with the reason.
  • The script inventory with an owner per script, and DNS and email items addressed to whoever manages the domain.
  • A rescan date, because marketing teams add scripts every month. The sample report shows one layout, and severity, confidence and verification explains how to label what you have not confirmed.

A ScanBastion scan lists Webflow under technologies detected when the site carries Webflow's generator tag, and covers headers, TLS, DNS, third-party scripts and forms in one pass. Run a scan on the client's site, or check its headers first with the free headers and TLS checker.