SaaS Ranking

HTTPS enforced with HSTS in Content management systems

We measure this ourselves on their own site. It is the cheapest security control there is.

27 of 45 companies we measured here publish it, that is 60%. Last checked 2026-10-17.

60% here against 62% across every category we measure. Content management systems sits below the overall share for this criterion.

This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.

Back to HTTPS enforced with HSTS across all categories, or to Content management systems.

The evidence at a glance
  • Found27
  • Not found at checked addresses18
  • Not measured0

45 companies in total. Unmeasured companies are excluded from the published share.

Published

HTTP redirects to HTTPS and the HSTS header is set.

VendorWhat we found
ButterCMS https://buttercms.com/Checked
CloudCannon https://cloudcannon.com/Checked
Concrete CMS https://concretecms.com/Checked
CoreMedia https://coremedia.com/Checked
Craft CMS https://craftcms.com/Checked
Decap CMS https://decapcms.org/Checked
Directus https://directus.io/Checked
Drupal https://drupal.org/Checked
Grav https://getgrav.org/Checked
Hygraph https://hygraph.com/Checked
Ibexa https://ibexa.co/Checked
Jadu Central https://jadu.net/Checked
Joomla https://joomla.org/Checked
Kontent.ai https://kontent.ai/Checked
Magnolia https://magnolia-cms.com/Checked
Payload https://payloadcms.com/Checked
Plasmic https://plasmic.app/Checked
Prismic https://prismic.io/Checked
Progress Sitefinity https://progress.com/Checked
Sanity https://sanity.io/Checked
Shorthand https://shorthand.com/Checked
Storyblok https://storyblok.com/Checked
Strapi https://strapi.io/Checked
Tina https://tina.io/Checked
TYPO3 https://typo3.com/Checked
Umbraco https://umbraco.com/Checked
Uniform https://uniform.dev/Checked
No enforced HTTPS with HSTS found.

We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.

VendorWhat we found
Builder.io 2 addresses checkedChecked
Cockpit 2 addresses checkedChecked
Contentful 2 addresses checkedChecked
Contentstack 2 addresses checkedChecked
Damibu Feeds 2 addresses checkedChecked
DatoCMS 2 addresses checkedChecked
Enonic 2 addresses checkedChecked
FirstSpirit 2 addresses checkedChecked
Kentico 2 addresses checkedChecked
Keystone 2 addresses checkedChecked
OGGEH 2 addresses checkedChecked
Pantheon 2 addresses checkedChecked
ProcessWire 2 addresses checkedChecked
QuickSilk 2 addresses checkedChecked
Silverstripe 2 addresses checkedChecked
Squiz 2 addresses checkedChecked
Statamic 2 addresses checkedChecked
Write.as 2 addresses checkedChecked
Not measured

We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.

None. Every vendor here was measured for this criterion.

Other criteria in Content management systems

HTTPS enforced with HSTS in related categories

Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.