WordPress plugin comparison
CCS-HTTPS vs Protocol Enforcer
At a glance
- CCS-HTTPS has more active installs: 10+, against fewer than 10 for Protocol Enforcer.
- On a typical day, CCS-HTTPS is downloaded about 5 times, Protocol Enforcer about 1.
- Protocol Enforcer has no reviews yet.
- Protocol Enforcer was updated more recently: Aug 11, 2016, against Dec 19, 2014 for CCS-HTTPS.
- Protocol Enforcer is tested with a newer WordPress: 4.6.30, against 4.1.42 for CCS-HTTPS.
- CCS-HTTPS has been around longer: since 2012, against 2016 for Protocol Enforcer.
Line by line
Level: each leads on 2 of 4 comparable lines.
| Metric |  CCS-HTTPS |  Protocol Enforcer |
|---|---|---|
| Popular rank | #47,609 | – |
| Active installs | 10+ | Fewer than 10 |
| Downloads, last 30 days | 141 | 22 |
| Rating | 3.0(2) | No ratings |
| Support threads resolved | – | – |
| Tested up to | 4.1.42 | 4.6.30 |
| Search multiplier | ×0.00 | ×0.00 |
| Last release | 12 years ago | 10 years ago |
| Requires PHP | – | – |
From WordPress.org's public data, refreshed every night. Downloads are WordPress.org's official daily figures for the last 30 days.
Tags they share
More comparisons
- CCS-HTTPS vs Mavis HTTPS to HTTP Redirection
- CCS-HTTPS vs Easy HTTPS Redirection (SSL)
- CCS-HTTPS vs WP Force SSL & HTTPS SSL Redirect
- CCS-HTTPS vs WP Encryption
- Protocol Enforcer vs Mavis HTTPS to HTTP Redirection
- Protocol Enforcer vs HTTPS for WordPress
- Protocol Enforcer vs PRyC WP
- Protocol Enforcer vs LCS HTTPS
Is one of these yours?
Track your plugin against its rivals every day: rank, installs, downloads, ratings and their releases, with alerts when anything moves.
Start free