Census › Plugin profiles › SSL Insecure Content Fixer
SSL Insecure Content Fixer
Figures from the Plugin Directory Census · as of 28 Aug 2026
100,000
Active installs, lower bound
Group: 100,000 to 999,999 installs
108
Days since the last release
Group median: 12
4.8
out of 5, from 221 ratings
Group median: 4.7 (10+ ratings)
no threads
Support threads, two months
Group: 68.2%
Full profile on wordpress.orgShow on the mapCompare with your own plugins
What is SSL Insecure Content Fixer and who is behind it?
SSL Insecure Content Fixer is a WordPress plugin in the “Security” field, made by webaware. It has been listed in the directory since 20 Apr 2012, so for 14 years. webaware has 2 plugins with at least 10,000 installs in the census. With 100,000 to 199,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 108 days before the reference date, and it is tested up to WordPress 7.0.
This is how the author describes the plugin on wordpress.org:
“Clean up WordPress website HTTPS insecure content”
Self-description on wordpress.org, retrieved on 10 Sept 2026
When was SSL Insecure Content Fixer last released?
The last release of SSL Insecure Content Fixer came 108 days before the reference date; the group median is 12 days.
How many installs does SSL Insecure Content Fixer have?
SSL Insecure Content Fixer had 100,000 to 199,999 active installs on the reference date. Within its group, 219 plugins had a higher band and 179 plugins the same band.
The API reports installs only as a lower bound with one significant figure: 100,000 means at least 100,000 and at most 199,999.
Which WordPress version is SSL Insecure Content Fixer tested with?
No directory notice: tested up to WordPress 7.0, while core stood at 7.1 on the reference date. The notice appears once the field falls below 6.9; that applied to 8.0% of the group.
How does SSL Insecure Content Fixer compare with its group?
The group holds 399 listed plugins. 86.2% of them had a more recent last release than SSL Insecure Content Fixer; 5.3% had no release for more than 365 days.
| Figure | SSL Insecure Content Fixer | Group, 399 plugins |
|---|---|---|
| Days since the last release | 108 | median 12 |
| Rating | 4.8 (221) | median 4.7 (10+ ratings) |
| Support threads marked resolved | not stated | 68.2% |
| Tested up to | 7.0 | 47.6% on 7.1 |
| Requires PHP | 5.3 | most often 7.4 (41.6%) |
All values on the reference date
| Slug | ssl-insecure-content-fixer |
|---|---|
| Author | webaware |
| Active installs | 100,000 to 199,999 |
| Last release | 108 days before the reference date |
| Tested up to | WordPress 7.0 · core on the reference date: 7.1 |
| Requires WordPress | 4.0 |
| Requires PHP | 5.3 |
| Rating | 4.8 out of 5 from 221 ratings |
| Support threads, two months | none in the window |
| Listed since | 20 Apr 2012 |
| Total downloads | 2,670,527, updates included |
| Tags | https, insecure-content, mixed-content, partially-encrypted, ssl |
Tags
| Tag | Plugins with 10,000+ installs and this tag | Rank by installs | Median days since release |
|---|---|---|---|
| https | 7 | 3 | 11 |
| insecure-content | 2 | 1 | 60 |
| mixed-content | 4 | 1 | 59 |
| partially-encrypted | 1 | 1 | 108 |
| ssl | 9 | 2 | 48 |
Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.
Class of 2012
SSL Insecure Content Fixer has been listed since 20 Apr 2012. Of the 139 plugins with 10,000+ installs added in 2012, 78.4% released within the 365 days before the reference date.
Same group, shared tags
Not a recommendation; the same figures for comparison. Alphabetical.
| Plugin | Active installs | Last release | Rating |
|---|---|---|---|
| Cloudflare | 200,000 to 299,999 | 46 days before the reference date | 3.5 (180) |
| Easy HTTPS Redirection | 100,000 to 199,999 | 11 days before the reference date | 4.2 (71) |
| Flexible SSL for CloudFlare | 100,000 to 199,999 | 248 days before the reference date | 4.8 (51) |
| Hostinger Tools | 3,000,000 to 3,999,999 | 3 days before the reference date | 3.5 (40) |
| Really Simple Security | 3,000,000 to 3,999,999 | 4 days before the reference date | 4.9 (8,862) |
Do you maintain SSL Insecure Content Fixer?
If you maintain SSL Insecure Content Fixer, you can link to this profile, for example from your readme or your website. Both snippets show this badge:
HTML
<a href="https://hafenstudios.com/en/census/plugins/ssl-insecure-content-fixer/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="SSL Insecure Content Fixer in the Plugin Directory Census 01/2026" width="220" height="40"></a>
Markdown
[](https://hafenstudios.com/en/census/plugins/ssl-insecure-content-fixer/)
The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.
A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.
How to cite
hafenstudios (2026): SSL Insecure Content Fixer, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/ssl-insecure-content-fixer/
Source and status
All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.
Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.
