Make password-reset emails clear and secure
A good recovery email is easy to understand, while the underlying flow limits token exposure and abuse.

On this page
Protect the request flow
Return a consistent response whether or not the submitted account exists, and avoid revealing the answer through response timing. Apply rate limiting or equivalent controls so the recovery endpoint cannot be used to flood an inbox.
Generate reset tokens with a cryptographically secure random source, store them securely, and make them single-use with an appropriate expiry. These decisions belong in the authentication system, not in the email template.
Explain one action without adding noise
Name the product, state that a password reset was requested, and provide one clearly labeled action. Explain when the link expires using the actual policy implemented by the application. Avoid inventing a time limit in the copy that differs from the token’s lifetime.
Include a short explanation for someone who did not request the message. Keep promotional sections out of this email. A person trying to regain access needs a clear route back to their account, not an onboarding campaign.
Review the entire link lifecycle
Build reset links from a trusted application origin using HTTPS. Avoid exposing tokens in analytics or routine logs. After a successful reset, notify the user without including their password, and handle existing sessions according to your recovery policy.
Test expired links, reused links, multiple reset requests, and a recipient opening the email on a different device. Confirm that every outcome has understandable copy and a safe next step. The email and the recovery screen should feel like one coherent interaction.
Keep this template small enough that a reviewer can assess it alongside the authentication flow. Security properties are easier to preserve when the message, token policy, and destination behavior are reviewed together.
