[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fhz8rP9vETXwSo_MUfDeNS0KgVsRv9YLBgHkErcWRLQ8":3,"$fyZWZkjJtXAVoa3aIDOdhAAZi2rrE45L8ZsvqOfdkwa4":182,"$fyNJn39D4xh6Pgdjq4zoCGUSd5c3gLsg_32clQ_-e5vQ":187},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":37,"analysis":134,"fingerprints":168},"ssl-fixer","SSL Fixer","0.3","Frank","https:\u002F\u002Fprofiles.wordpress.org\u002Flaitskin\u002F","\u003Cp>SSL Fixer makes a few changes to the database in order to fix any insecure links. Effectively fixing the HTTPS redirection and mixed content problems in one click. Precisely speaking it does two things:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Modify any insecure links from your wp-config.php file, such as WP_DEFINE() home and siteurl.\u003C\u002Fli>\n\u003Cli>Convert all your database’s HTTP links into HTTPS ones, making the requests secure.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>To make these changes, all you need to do is click the plugin’s “Fix SSL” button.\u003C\u002Fp>\n","SSL Fixer makes a few changes to the database in order to fix any insecure links. Effectively fixing the HTTPS redirection and mixed content problems  &hellip;",100,4068,0,"2021-03-12T20:35:00.000Z","5.7.15","4.7","7.0",[19,20,21,22,23],"fix","https","insecure","mixed-content","ssl","https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fssl-fixer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fssl-fixer.zip",85,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"laitskin",1,30,84,"2026-08-29T16:26:36.311Z",[38,59,79,95,114],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":57,"download_link":58,"security_score":11,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"ssl-insecure-content-fixer","SSL Insecure Content Fixer","2.7.2","webaware","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebaware\u002F","\u003Cp>Clean up your WordPress website’s HTTPS insecure content and mixed content warnings. Installing the SSL Insecure Content Fixer plugin will solve most insecure content warnings with little or no effort. The remainder can be diagnosed with a few simple tools.\u003C\u002Fp>\n\u003Cp>When you install SSL Insecure Content Fixer, its default settings are activated and it will automatically perform some basic fixes on your website using the Simple fix level. You can select more comprehensive fix levels as needed by your website.\u003C\u002Fp>\n\u003Cp>WordPress Multisite gets a network settings page. This can be used to set default settings for all sites within a network, so that network administrators only need to specify settings on sites that have requirements differing from the network defaults.\u003C\u002Fp>\n\u003Cp>See the \u003Ca href=\"https:\u002F\u002Fssl.webaware.net.au\u002F\" rel=\"nofollow ugc\">SSL Insecure Content Fixer website\u003C\u002Fa> for more details.\u003C\u002Fp>\n\u003Ch3>Translations\u003C\u002Fh3>\n\u003Cp>Many thanks to the generous efforts of our translators:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Bulgarian (bg_BG) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fbg\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the Bulgarian translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Chinese simplified (zh_CN) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fzh-cn\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the Chinese translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>English (en_CA) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-ca\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the English (Canadian) translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>English (en_GB) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-gb\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the English (British) translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>English (en_ZA) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-za\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the English (South African) translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Dutch (nl_NL) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fnl\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the Dutch translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>German (de_DE) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fde\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the German translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>French (fr_FR) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Ffr\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the French translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Italian (it_IT) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fit\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the Italian translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Japanese (ja) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fja\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the Japanese translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Russian (ru_RU) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fru\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the Russian translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Spanish (es_ES) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fes\u002Fdefault\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">the Spanish translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you’d like to help out by translating this plugin, please \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fssl-insecure-content-fixer\" rel=\"nofollow ugc\">sign up for an account and dig in\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>SSL Insecure Content Fixer does not collect any personally identifying information, and does not set any cookies.\u003C\u002Fp>\n","Clean up WordPress website HTTPS insecure content",100000,2666646,96,221,"2026-05-12T05:29:00.000Z","7.0.2","4.0","5.3",[20,55,22,56,23],"insecure-content","partially-encrypted","https:\u002F\u002Fssl.webaware.net.au\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fssl-insecure-content-fixer.2.7.2.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":69,"num_ratings":70,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":74,"tags":75,"homepage":77,"download_link":78,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"http-https-remover","SSL Mixed Content Fix","3.2.8","Steve85b","https:\u002F\u002Fprofiles.wordpress.org\u002Fsteve85b\u002F","\u003Cp>\u003Cstrong>Try it out on your free dummy site: Click here => \u003Ca href=\"https:\u002F\u002Ftastewp.com\u002Fplugins\u002Fhttp-https-remover\" rel=\"nofollow ugc\">https:\u002F\u002Ftastewp.com\u002Fplugins\u002Fhttp-https-remover\u003C\u002Fa>.\u003C\u002Fstrong>\u003Cbr \u002F>\n(this trick works for all plugins in the WP repo – just replace “wordpress” with “tastewp” in the URL)\u003C\u002Fp>\n\u003Cp>UPDATE: This plugin will be maintained again! It changed ownership and we’re currently collecting ideas how to further improve it. If you have any cool ideas, please let us know in Support Forum. Thank you!\u003C\u002Fp>\n\u003Cp>Major updated in the latest release (3.0):\u003Cbr \u002F>\n– Plugin has a proper settings page now\u003Cbr \u002F>\n– Many bugs fixed\u003Cbr \u002F>\n– Code optimized, causing performance to increase a lot\u003C\u002Fp>\n\u003Cp>Main features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Works in Front- and Backend\u003C\u002Fli>\n\u003Cli>Makes every Plugin compatible with https\u003C\u002Fli>\n\u003Cli>Compatible with WPBakery & Disqus\u003C\u002Fli>\n\u003Cli>Fixes Google Fonts issues\u003C\u002Fli>\n\u003Cli>Makes your website faster\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What does this Plugin do?\u003C\u002Fh4>\n\u003Cp>With protocol relative url’s you simply leave off the http: or https: part of the resource path. The browser will automatically load the resource using the same protocol that the page was loaded with.\u003C\u002Fp>\n\u003Cp>For example, an absolute url may look like\u003C\u002Fp>\n\u003Cpre>\u003Ccode>src=\"http:\u002F\u002Fdomain.com\u002Fscript.js\"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you were to load this from a https page the script will not be loaded – as non-https resources are not loaded from https pages (for security reasons).\u003C\u002Fp>\n\u003Cp>The protocol relative url would look like\u003C\u002Fp>\n\u003Cpre>\u003Ccode>src=\"\u002F\u002Fdomain.com\u002Fscript.js\"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>and would load if the web page was http or https.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Tipp:\u003C\u002Fstrong> Check your Settings -> General page and make sure your WordPress Address and Site Address are starting with “https”.\u003Cbr \u002F>\nAdd the following two lines in your wp-config.php above the line that​ says “Stop Editing Here”:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('FORCE_SSL', true);\ndefine('FORCE_SSL_ADMIN',true);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>What is Mixed Content?\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Mixed content\u003C\u002Fstrong> occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS. Modern browsers display warnings about this type of content to indicate to the user that this page contains insecure resources.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note: You should always protect all of your websites with HTTPS, even if they don’t handle sensitive communications.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Example\u003C\u002Fh4>\n\u003Cp>Without Plugin:\u003Cbr \u002F>\n    src=”http:\u002F\u002Fdomain.com\u002Fscript01.js”\u003Cbr \u002F>\n    src=”https:\u002F\u002Fdomain.com\u002Fscript02.js”\u003Cbr \u002F>\n    src=”\u002F\u002Fdomain.com\u002Fscript03.js”\u003C\u002Fp>\n\u003Cp>With Plugin:\u003Cbr \u002F>\n    src=”\u002F\u002Fdomain.com\u002Fscript01.js”\u003Cbr \u002F>\n    src=”\u002F\u002Fdomain.com\u002Fscript02.js”\u003Cbr \u002F>\n    src=”\u002F\u002Fdomain.com\u002Fscript03.js”\u003C\u002Fp>\n\u003Ch4>If using Cache Plugins\u003C\u002Fh4>\n\u003Cp>If the plugin isn’t working like expected please purge\u002Fclear cache for the changes to take effect!\u003C\u002Fp>\n","A fix for mixed content! This Plugin creates protocol relative urls by removing http + https from links. Works in Front- and Backend!",8000,325754,82,34,"2024-07-17T01:21:00.000Z","6.6.5","4.6","",[76,20,55,22,23],"force-ssl","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fhttp-https-Removal\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhttp-https-remover.3.2.8.zip",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":46,"downloaded":87,"rating":35,"num_ratings":88,"last_updated":89,"tested_up_to":51,"requires_at_least":90,"requires_php":74,"tags":91,"homepage":93,"download_link":94,"security_score":11,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"https-redirection","Easy HTTPS Redirection (SSL)","2.0.1","mra13 \u002F Team Tips and Tricks HQ","https:\u002F\u002Fprofiles.wordpress.org\u002Fmra13\u002F","\u003Ch4>Only use this plugin if you have installed SSL certificate on your site and HTTPS is working correctly\u003C\u002Fh4>\n\u003Cp>Once you’ve installed an SSL certificate on your site, it’s important to ensure that your webpages are accessed via their secure HTTPS URLs.\u003C\u002Fp>\n\u003Cp>To improve SEO and user security, you want search engines and visitors to always use the HTTPS version of your pages. This plugin makes that easy by automatically redirecting users to the HTTPS version whenever they try to access the non-HTTPS (HTTP) version of a page.\u003C\u002Fp>\n\u003Ch3>Example\u003C\u002Fh3>\n\u003Cp>Let’s say you want to ensure the following page is always accessed over HTTPS:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>https:\u002F\u002Fwww.example.com\u002Fcheckout\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If a visitor tries to access:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>http:\u002F\u002Fwww.example.com\u002Fcheckout\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The plugin will automatically redirect them to the secure version:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>https:\u002F\u002Fwww.example.com\u002Fcheckout\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This ensures that visitors always access the HTTPS version of your pages or site.\u003C\u002Fp>\n\u003Cp>You can choose to automatically redirect your entire domain to HTTPS, or selectively apply HTTPS redirection to specific pages.\u003C\u002Fp>\n\u003Ch3>Video Tutorials\u003C\u002Fh3>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FoyJgRFCM6u8?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FLtyBraB64v8?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Ch3>Force Load Static Files Using HTTPS\u003C\u002Fh3>\n\u003Cp>If you started using SSL from day 1 of your site then all your static files are already embedded using HTTPS URL. You have no issue there.\u003C\u002Fp>\n\u003Cp>However, if you have an existing website where you have a lot of static files that are embedded in your posts and pages using NON-HTTPS URL then you will need to change those. Otherwise, the browser will show an SSL warning to your visitors.\u003C\u002Fp>\n\u003Cp>This plugin has an option that will allow you to force load those static files using HTTPS URL dynamically.\u003C\u002Fp>\n\u003Cp>This will help you make the webpage fully compatible with SSL.\u003C\u002Fp>\n\u003Ch3>Mixed Content Scanner & Database URL Fixer\u003C\u002Fh3>\n\u003Cp>After switching to HTTPS, your pages can still trigger browser “mixed content” warnings if old HTTP URLs remain saved in your database (in post content, custom post types, post meta, or WordPress options). This plugin includes a built-in scanner to find and update those insecure URLs to their HTTPS version – no manual database editing required.\u003C\u002Fp>\n\u003Cp>Available from the \u003Cstrong>Mixed Contents\u003C\u002Fstrong> settings tab, the scanner lets you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Scan selected post types\u003C\u002Fstrong> – Choose exactly which post types to scan and update, including posts, pages, and any custom post types registered by your other plugins (products, orders, downloads, subscriptions, and more).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Update other database tables\u003C\u002Fstrong> – Optionally include the WordPress options table in the scan.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Include post meta\u003C\u002Fstrong> – Extend the scan to post meta for the selected post types.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Choose your scan scope\u003C\u002Fstrong> – Run a quick “Scan Static Resources Only” pass, or a thorough “Scan All” to catch every non-HTTPS reference.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This makes cleaning up legacy HTTP links straightforward, helping you achieve a fully secure padlock with no mixed content errors.\u003C\u002Fp>\n\u003Ch3>SSL Certificate Expiry Notification\u003C\u002Fh3>\n\u003Cp>This plugin includes a feature that allows you to receive email notifications when your SSL certificate is about to expire. It helps ensure your website remains secure and accessible over HTTPS.\u003C\u002Fp>\n\u003Cp>You can configure the recipient email address and specify how many days in advance the notification should be sent. By default, the notification is sent 7 days before expiry, but you can adjust this to suit your preference.\u003C\u002Fp>\n\u003Cp>This feature is especially useful for site owners who may not frequently check their SSL status, or for those managing multiple websites. By receiving timely alerts, you can renew your SSL certificate in advance and prevent potential downtime or security warnings.\u003C\u002Fp>\n\u003Ch3>HTTP Strict Transport Security (HSTS) Support\u003C\u002Fh3>\n\u003Cp>Easy HTTPS Redirection includes built-in support for sending the HTTP Strict Transport Security (HSTS) response header.\u003C\u002Fp>\n\u003Cp>HSTS instructs compatible web browsers to automatically access your website over HTTPS after a visitor has successfully visited your secure site. This helps strengthen your site’s HTTPS enforcement and reduces the risk of users accidentally accessing the HTTP version of your website.\u003C\u002Fp>\n\u003Cp>The plugin allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable or disable the HSTS response header with a simple checkbox.\u003C\u002Fli>\n\u003Cli>Configure the HSTS max-age value.\u003C\u002Fli>\n\u003Cli>Apply the HSTS policy to all subdomains using the \u003Ccode>includeSubDomains\u003C\u002Fcode> directive.\u003C\u002Fli>\n\u003Cli>Include the \u003Ccode>preload\u003C\u002Fcode> directive for sites that intend to submit their domain to the browser HSTS preload list.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Automatically redirect all HTTP traffic to HTTPS\u003C\u002Fli>\n\u003Cli>Option to force HTTPS on the entire site\u003C\u002Fli>\n\u003Cli>Option to selectively apply HTTPS redirection to specific pages\u003C\u002Fli>\n\u003Cli>Helps search engines index the secure versions of your pages\u003C\u002Fli>\n\u003Cli>Improves site security and user trust\u003C\u002Fli>\n\u003Cli>Force load static files (images, js, css etc) using a HTTPS URL\u003C\u002Fli>\n\u003Cli>Built-in mixed content scanner to find and update non-HTTPS URLs across post content, post meta, custom post types, and WordPress options\u003C\u002Fli>\n\u003Cli>SSL certificate expiry notification – Option to send SSL expiry notifications to a specific email address\u003C\u002Fli>\n\u003Cli>Easily see which SSL certificates on your site are approaching their expiry date.\u003C\u002Fli>\n\u003Cli>HTTP Strict Transport Security (HSTS) support with configurable max-age, includeSubDomains, and preload options.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>View more details on the \u003Ca href=\"https:\u002F\u002Fwww.tipsandtricks-hq.com\u002Fwordpress-easy-https-redirection-plugin\" rel=\"nofollow ugc\">HTTPS Redirection plugin\u003C\u002Fa> page.\u003C\u002Fp>\n","The plugin allows an automatic redirection to the \"HTTPS\" version\u002FURL of the site. Make your site SSL compatible easily.",1239012,71,"2026-06-30T15:10:00.000Z","6.5",[76,20,55,92,23],"redirection","https:\u002F\u002Fwww.tipsandtricks-hq.com\u002Fwordpress-easy-https-redirection-plugin","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhttps-redirection.2.0.1.zip",{"slug":96,"name":97,"version":98,"author":99,"author_profile":100,"description":101,"short_description":102,"active_installs":103,"downloaded":104,"rating":105,"num_ratings":106,"last_updated":107,"tested_up_to":51,"requires_at_least":73,"requires_php":108,"tags":109,"homepage":111,"download_link":112,"security_score":11,"vuln_count":33,"unpatched_count":13,"last_vuln_date":113,"fetched_at":28},"wp-force-ssl","WP Force SSL & HTTPS SSL Redirect","1.70","WebFactory","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebfactory\u002F","\u003Cp>\u003Ca href=\"https:\u002F\u002Fwpforcessl.com\u002F?ref=wporg\" rel=\"nofollow ugc\">WP Force SSL\u003C\u002Fa> helps you redirect insecure HTTP traffic to secure HTTPS and fix SSL errors \u003Cstrong>without touching any code\u003C\u002Fstrong>. Activate Force SSL and everything will be set and SSL enabled. The entire site will move to HTTPS using your SSL certificate. It works with any SSL certificate. It can be free SSL certificate from Let’s Encrypt or a paid SSL certificate.\u003C\u002Fp>\n\u003Cp>How to add SSL & enable SSL? Most hosting companies support the free SSL certificate from Let’s Encrypt, so login to your hosting panel and add SSL certificate. You’ll see a button labeled “Add SSL Certificate” or “Add Let’s Encrypt Certificate” and after that it’s 1 click to have the SSL enabled on your site with WP Force SSL. If that doesn’t work get \u003Ca href=\"https:\u002F\u002Fwpforcessl.com\u002F\" rel=\"nofollow ugc\">WP Force SSL PRO\u003C\u002Fa> and it’ll generate free SSL certificate for your site. And will regenerate SSL certificate every 90 days.\u003C\u002Fp>\n\u003Cp>Access WP Force SSL settings via the main Settings menu -> WP Force SSL.\u003C\u002Fp>\n\u003Ch4>SSL Tests available in the plugin\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>is site on localhost?\u003C\u002Fli>\n\u003Cli>check SSL certificate\u003C\u002Fli>\n\u003Cli>check SSL certificate expiry date\u003C\u002Fli>\n\u003Cli>is latest version of Force SSL used?\u003C\u002Fli>\n\u003Cli>are known incompatible SSL plugins active?\u003C\u002Fli>\n\u003Cli>is WP address URL set for SSL?\u003C\u002Fli>\n\u003Cli>is WP home URL set for SSL?\u003C\u002Fli>\n\u003Cli>is SSL monitoring enabled (pro feature)\u003C\u002Fli>\n\u003Cli>is HTTPS redirection working?\u003C\u002Fli>\n\u003Cli>is file redirection working (pro feature)\u003C\u002Fli>\n\u003Cli>is HSTS enabled?\u003C\u002Fli>\n\u003Cli>check mixed-content issue (pro feature)\u003C\u002Fli>\n\u003Cli>is htaccess available & writable?\u003C\u002Fli>\n\u003Cli>is 404 redirection enabled (pro feature)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>redirect HTTP to HTTPS\u003C\u002Fli>\n\u003Cli>fix mixed-content (pro)\u003C\u002Fli>\n\u003Cli>enable HSTS\u003C\u002Fli>\n\u003Cli>force secure cookies (pro)\u003C\u002Fli>\n\u003Cli>cross-site scripting protection (pro)\u003C\u002Fli>\n\u003Cli>expect CT header\u003C\u002Fli>\n\u003Cli>X-Frame options\u003C\u002Fli>\n\u003Cli>show WP Force SSL menu in admin bar\u003C\u002Fli>\n\u003Cli>show WP Force SSL widget in admin dashboard\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>SSL certificate testing tool\u003C\u002Fh4>\n\u003Cp>WP Force SSL comes with an SSL certificate testing tool. It tests if the SSL certificate is valid, properly installed & up-to date.\u003C\u002Fp>\n\u003Ch4>Need support?\u003C\u002Fh4>\n\u003Cp>We’re here for you! Things get frustrating when they don’t work so make sure you \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-force-ssl\u002F\" rel=\"ugc\">open a support topic\u003C\u002Fa> in the official Force SSL forum. We answer all questions within a few hours!\u003C\u002Fp>\n\u003Ch4>External Assets\u003C\u002Fh4>\n\u003Cp>A big thank you to \u003Ca href=\"https:\u002F\u002Fsweetalert2.github.io\u002F\" rel=\"nofollow ugc\">SweetAlert2\u003C\u002Fa> authors which we use to make alerts nicer. And to \u003Ca href=\"https:\u002F\u002Fdepositphotos.com\u002F248496280\u002Fstock-illustration-online-payment-protection-system-concept.html\" rel=\"nofollow ugc\">DepositPhotos\u003C\u002Fa> for the lovely header image.\u003C\u002Fp>\n","Enable SSL & HTTPS redirect with 1 click! Add SSL certificate & WP Force SSL to redirect site from HTTP to HTTPS & fix SSL errors.",90000,1835602,94,179,"2026-07-20T05:44:00.000Z","5.2",[76,20,22,23,110],"ssl-certificate","https:\u002F\u002Fwpforcessl.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-force-ssl.1.70.zip","2024-06-07 00:00:00",{"slug":115,"name":116,"version":117,"author":118,"author_profile":119,"description":120,"short_description":121,"active_installs":122,"downloaded":123,"rating":124,"num_ratings":125,"last_updated":126,"tested_up_to":51,"requires_at_least":73,"requires_php":74,"tags":127,"homepage":130,"download_link":131,"security_score":132,"vuln_count":33,"unpatched_count":13,"last_vuln_date":133,"fetched_at":28},"one-click-ssl","One Click SSL","1.7.8","Tribulant Software","https:\u002F\u002Fprofiles.wordpress.org\u002Fcontrid\u002F","\u003Cp>A simple and easy to use WordPress SSL plugin which will redirect all non-SSL pages to SSL\u002FTLS and ensure that all resources on your SSL pages are loaded over SSL as well.\u003C\u002Fp>\n\u003Cp>It includes a user-friendly setup wizard upon activation to check if SSL is supported on the hosting\u002Fserver before it allows the SSL to be enabled and that ensures that the website doesn’t become inaccessible if SSL is not supported.\u003C\u002Fp>\n\u003Ch4>Plugin Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Check if SSL\u002FTLS is supported on hosting\u002Fserver\u003C\u002Fli>\n\u003Cli>Enable SSL with a single click\u003C\u002Fli>\n\u003Cli>Redirects all non-SSL URLs to https:\u002F\u002F\u003C\u002Fli>\n\u003Cli>Converts all non-SSL resources (images, scripts, stylesheets, etc.) to https:\u002F\u002F on pages\u003C\u002Fli>\n\u003Cli>Redirect to non-SSL if SSL is not enabled\u003C\u002Fli>\n\u003Cli>Multisite network compatibility (enable SSL for all sites from one location)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See our \u003Ca href=\"https:\u002F\u002Ftribulant.com\u002Fdocs\u002Fone-click-ssl-plugin\u002F11098\" rel=\"nofollow ugc\">online documentation\u003C\u002Fa> for more details and detailed instructions.\u003C\u002Fp>\n","Enable SSL\u002FTLS (https:\u002F\u002F) to redirect all pages to SSL\u002FTLS and load all resources over SSL\u002FTLS.",10000,316811,98,139,"2026-06-19T19:58:00.000Z",[20,22,128,129,23],"redirect","resources","https:\u002F\u002Ftribulant.com\u002Fplugins\u002Fview\u002F18\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fone-click-ssl.1.7.8.zip",99,"2019-07-11 00:00:00",{"attackSurface":135,"codeSignals":152,"taintFlows":160,"riskAssessment":161,"analyzedAt":167},{"hooks":136,"ajaxHandlers":148,"restRoutes":149,"shortcodes":150,"cronEvents":151,"entryPointCount":13,"unprotectedCount":13},[137,143],{"type":138,"name":139,"callback":140,"file":141,"line":142},"action","admin_menu","sf_admin_menu","sf-admin.php",2,{"type":138,"name":144,"callback":145,"file":146,"line":147},"admin_notices","activation_notice","sf-ssl-fixer.php",83,[],[],[],[],{"dangerousFunctions":153,"sqlUsage":154,"outputEscaping":157,"fileOperations":142,"externalRequests":13,"nonceChecks":33,"capabilityChecks":33,"bundledLibraries":159},[],{"prepared":155,"raw":13,"locations":156},4,[],{"escaped":13,"rawEcho":13,"locations":158},[],[],[],{"summary":162,"deductions":163},"The \"ssl-fixer\" v0.3 plugin exhibits a strong security posture based on the provided static analysis. The absence of any detected attack surface entries, such as AJAX handlers, REST API routes, or shortcodes without authentication checks, is a significant positive indicator. Furthermore, the code demonstrates excellent practices by not utilizing dangerous functions, employing prepared statements for all SQL queries, and properly escaping all output. The presence of nonce and capability checks further reinforces its secure design. The vulnerability history is also clean, with no known CVEs, indicating a lack of past exploitable issues.\n\nWhile the static analysis shows no concerning taint flows or exploitable pathways, the plugin does perform two file operations. Without further context on these operations, it's difficult to ascertain any potential risks. However, given the overall secure coding practices observed, the likelihood of these file operations being a significant vulnerability is low. The plugin's lack of bundled libraries is also a positive, as it avoids the potential risks associated with outdated or vulnerable third-party code. In conclusion, \"ssl-fixer\" v0.3 appears to be a securely coded plugin with a negligible risk profile, primarily due to its minimal attack surface, robust security checks, and clean vulnerability history.",[164],{"reason":165,"points":166},"File operations present",3,"2026-03-16T20:42:16.609Z",{"wat":169,"direct":174},{"assetPaths":170,"generatorPatterns":171,"scriptPaths":172,"versionParams":173},[],[],[],[],{"cssClasses":175,"htmlComments":176,"htmlAttributes":177,"restEndpoints":178,"jsGlobals":179,"shortcodeOutput":180},[],[],[],[],[],[181],"\u003Cinput type=\"hidden\" name=\"fixme\" value=\"fixme\">",{"error":183,"url":184,"statusCode":185,"statusMessage":186,"message":186},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fssl-fixer\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":13,"versions":188},[]]