HTTPS enforced with HSTS in Scheduling
We measure this ourselves on their own site. It is the cheapest security control there is.
26 of 35 companies we measured here publish it, that is 74%. Last checked 2026-10-16.
74% here against 62% across every category we measure. Scheduling sits above 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 Scheduling.
- Found26
- Not found at checked addresses9
- Not measured0
35 companies in total. Unmeasured companies are excluded from the published share.
Published
HTTP redirects to HTTPS and the HSTS header is set.
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.
| Vendor | What we found |
|---|---|
| Appointlet | 2 addresses checkedChecked |
| BookingLive | 2 addresses checkedChecked |
| Clockwise | 2 addresses checkedChecked |
| Motion | 2 addresses checkedChecked |
| Picktime | 2 addresses checkedChecked |
| Set a Time | 2 addresses checkedChecked |
| TidyCal | 2 addresses checkedChecked |
| Vyte | 2 addresses checkedChecked |
| Zcal | 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 Scheduling
- Data processing agreement
- Subprocessor list
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- No third-party tracking before consent
- security.txt (RFC 9116)
- Notice before subprocessors change
- Named privacy contact
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.