Send certificate email from your own domain or provider
Verify a sending domain, or connect Cloudflare, Resend, SES, Postmark, SendGrid, Mailgun, or raw SMTP. Test the sender before an event.
The certificate email is part of the event's identity. For many programmes, that means it should come from the organisation's own domain, not a shared sender.
Custom email senders are now available on Pro.
Two setup paths
Verify DKIM, SPF, and DMARC records for a domain you control, with a recheck while DNS propagates. Or connect Cloudflare, Resend, Amazon SES, Postmark, SendGrid, Mailgun, or raw SMTP. Set the display name, reply-to address, and optional CC/BCC on certificate email. Send a test from the saved configuration before an event; CC and BCC are skipped for tests.
What to maintain
The domain and provider are yours. That is the trade-off for a recognisable sender and replies that reach the organisation's inbox. The test send and delivery health make the maintenance visible, and the provider's delivery webhook brings delivered, bounced, and failed sends into analytics.
Credentials are encrypted at rest. The shared Verifycate sender remains available on every plan.
Related