Was HTTPS Redirect, Security & SSL Scan Hacked?

No Publicly Reported Incidents. As of June 2026, HTTPS Redirect, Security & SSL Scan has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev. Nerq's automated security analysis rates HTTPS Redirect, Security & SSL Scan's security posture as strong (security dimension score: 90/100). Trust Score: 66/100 (B-). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score66/100 (B-)
Security Dimension90/100
PublisherWP Encryption SSL
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see HTTPS Redirect, Security & SSL Scan Trust Score on Nerq.

FAQ

Has HTTPS Redirect, Security & SSL Scan been hacked?
As of June 2026, HTTPS Redirect, Security & SSL Scan has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev.
How many CVEs does HTTPS Redirect, Security & SSL Scan have?
HTTPS Redirect, Security & SSL Scan has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is HTTPS Redirect, Security & SSL Scan safe to use after a breach?
With no reported breaches, HTTPS Redirect, Security & SSL Scan appears safe based on available data.
Where can I check HTTPS Redirect, Security & SSL Scan's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for HTTPS Redirect, Security & SSL Scan. View the full trust analysis at nerq.ai/safe/wp-letsencrypt-ssl.

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy