• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Input Enhancing visibility of protection status in WordPress Toolkit

Maarten

Golden Pleskian
Plesk Guru
Recently, Plesk added a vulnerability status feature to the WordPress Toolkit, which is a great step forward. However, both the vulnerability status and the protection status are currently accessed through the same link, making it harder to quickly find the protection details.

It would benefit users, especially those less familiar with these features, if Plesk were to separate these into two distinct links. This way, the protection status would be more visible and easier to access, helping users stay informed about the security of their WordPress installations without extra steps. Clearer access to these statuses could also address the concern about the perceived gaps in protection, such as with xmlrpc.php, making Plesk's security offerings feel more complete and transparent.

I've created a corresponding UserVoice request:
 
Last edited:
Back
Top