A first test email takes a few documented steps. Sending to real recipients waits on DNS verification, which the docs say can take up to 72 hours.
What this covers. Observed from public pages, the rendered sign-up page and the documentation on 20 Nov 2026. No account was created, so in-product screens are described from the company's own docs, and onboarding emails were not seen.
Sign-up path
- Homepage: 'Get started'Observed1One click from the header or hero to /signup.
- Form: 'Create a Resend account'Observed3'Log in with Google', 'Log in with GitHub', or Email and Password (12+ characters, mixed letters, numbers, symbols). Button: 'Create account'.
- Create an API keyFrom docs5Name the key, choose Sending access or Full access. The key can be viewed only once.
- Send a test emailFrom docs8Quickstart sends from onboarding@resend.dev. The test domain only delivers to the account's own email address.
- Add a domainFrom docs7Domains page, Add Domain, choose a region, then copy DKIM and SPF records to the DNS provider.
- Wait for DNS verificationFrom docs7Often within 15 minutes of adding the records, occasionally up to 72 hours, with a Restart verification button after that.
Where a new user could stall
Sending to anyone else needs a verified domain. Docs say verification is often 15 minutes but can take up to 72 hours, and needs DNS access.
Fix. Email accounts whose domain is still Pending after 24 hours, with their DNS provider's guide and a link to share the records with whoever owns DNS.
The quickstart sender onboarding@resend.dev only delivers to the account's own address. Other recipients get a 403 with a verify-a-domain message.
Fix. When an account gets its first 403 of this kind, show a dashboard banner and send an email that opens straight to Add Domain.
The introduction lists 'Your own domain, verified with Resend' first, before the API key, although the quickstart can send a test without a domain.
Fix. Reorder the introduction so a test email to yourself comes first and domain verification second, putting the first win before the DNS wait.
The 'Create a Resend account' page labels its social buttons 'Log in with Google' and 'Log in with GitHub'.
Fix. Label them 'Sign up with Google' and 'Sign up with GitHub' on the sign-up page, and compare completion against the current copy.
Trial terms
Offer
Time to first value
First value
First run
Empty states and setup
Not observedOnboarding emails
Not observedWhat already works
- Google and GitHub sign-up, the accounts developers already use
- Production access from day one, no sandbox approval
- 13 framework and language quickstarts, plus a CLI quickstart
How a sprint would measure it
Share of new accounts with a verified domain within 72 hours of sign-up, 20% holdout.