Skip to content

Anonymous

My feedback

4 results found

  1. 295 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    In Plesk 18.0.54, published July 18th, 2023, Plesk has added the ability to add Transport Layer Security Authentication (TLSA) DNS records to domains’ DNS zones in Plesk. Such records are most commonly used to implement DNS-based Authentication of Named Entities (DANE). With this update the most popular DANE scenario is covered in Plesk for Linux.

    Full DANE support including UI improvements for all supported operating systems and versions is planned to become available by the end of Q3/2023.

    -- PD

    An error occurred while saving the comment
    Anonymous commented  · 

    hurry up Plesk, time to implement this, it 2 *past* 12...

    Anonymous supported this idea  · 
  2. 30 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Oh yes, Plesk definitely needs ARC. Without ARC, e-mail forwarding is rendered useless if any sender (to a forwarded address) has implemented a DMARC policy other than none.

    This is not a matter of Plesk admins requiring this feature, this is a must-have if Plesk wants to continue to be used as a mail server. The internet is moving on, all major e-mail providers push the implementation of DMARC and support ARC.

    Since we cannot control sender domains we have no option to mitigate this issue on the Plesk side if e-mail forwards are in place.

    Please implement this!

    Anonymous supported this idea  · 
  3. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Implementation of this "feature" should not depend on popularity. It is the only right *and* secure way to redirect from non-www to www domain. If this is not done, then the HSTS header is never sent for the non-www version of the domain, allowing MITM attacks / stripping HTTPS.

    IMHO Plesk should use the secure way by default: redirect from HTTP to HTTPS first (allowing the HSTS header to be sent) and *then redirect from non-www to www.

    If there really are people who wish to not do this, avoid one redirect and immediately redirect to https://www.domain.tld, then allow them to override the secure default. IMHO this is over-optimization, as these days (with HTTP/2) there is not nearly as much overhead as there was before.

    Please fix this if this is not done already. :-)

    Anonymous supported this idea  · 
  4. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 

Feedback and Knowledge Base