WordPress plugin comparison
HTTPS for WordPress vs Protocol Enforcer
At a glance
- HTTPS for WordPress has more active installs: 30+, against fewer than 10 for Protocol Enforcer.
- On a typical day, HTTPS for WordPress is downloaded about 6 times, Protocol Enforcer about 1.
- Protocol Enforcer was updated more recently: Aug 11, 2016, against Jun 3, 2008 for HTTPS for WordPress.
- Protocol Enforcer is tested with a newer WordPress: 4.6.30, against 2.5 for HTTPS for WordPress.
- HTTPS for WordPress has been around longer: since 2008, against 2016 for Protocol Enforcer.
Line by line
Level: each leads on 2 of 4 comparable lines.
| Metric |  HTTPS for WordPress |  Protocol Enforcer |
|---|---|---|
| Popular rank | #23,713 | – |
| Active installs | 30+ | Fewer than 10 |
| Downloads, last 30 days | 129 | 22 |
| Rating | No ratings | No ratings |
| Support threads resolved | – | – |
| Tested up to | 2.5 | 4.6.30 |
| Search multiplier | ×0.00 | ×0.00 |
| Last release | 18 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
- HTTPS for WordPress vs Force non-SSL
- HTTPS for WordPress vs Easy HTTPS Redirection (SSL)
- HTTPS for WordPress vs SSL Insecure Content Fixer
- HTTPS for WordPress vs WP Force SSL & HTTPS SSL Redirect
- Protocol Enforcer vs Mavis HTTPS to HTTP Redirection
- Protocol Enforcer vs CCS-HTTPS
- 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