Skip to contentVerifycate
FixedRecipientsNo. 035

Catch invalid recipient emails before the send

Recipient email addresses are validated when they are imported, added, or edited, so obvious typos do not turn into bounces after the certificate is issued.

By Ashwin Shenoy · Founder and engineer

A certificate is only delivered if the email address is real. A missing domain, a trailing space, or a name accidentally pasted into the email column produces a failed send and a support message.

Recipient email addresses are now checked when they enter the workspace.

What changed

The import, add-recipient, and edit-recipient paths validate the address before saving it. A value that is not an email address is rejected with an error on the field, instead of being accepted and failing later at send time.

Existing records with an invalid address can be corrected from the recipient's details. The delivery health view still shows a bounce if a valid-looking address is rejected by the receiving server.

A note on what validation can prove

A valid format is not a guarantee of deliverability. A typo can still form a valid address on the wrong domain, and a mailbox can be full or disabled. Validation removes the obvious mistakes; delivery health and bounces handle the rest.

Related

← Back to all updates

Start issuing

Certificates people can prove.

Design once, issue in bulk or from your LMS, and give every recipient a public page anyone can verify.