# resend.com
13 of 13 indexed pages, ordered by how often the site's own
pages cite them. This is all of them.
Indexed by stealpage. Full record: https://stealpage.com/d/resend.com
---
## Resend · Email for developers
· 600 words
### Email for
developers
The best way to reach humans instead of spam folders. Deliver transactional and marketing emails at scale.
Companies of all sizes trust Resend to deliver their most important emails.
### Integrate
A simple, elegant interface so you can start sending emails in minutes. It fits right into your code with SDKs for your favorite programming languages.
### First-class
developer experience
We are a team of engineers who love building tools for other engineers.
Our goal is to create the email platform we've always wished we had — one that _just works_.
### Test mode
Simulate events and experiment with our API without the risk of accidentally sending real emails to real people.
[Learn more](https://resend.com/docs/dashboard/emails/send-test-emails)
### Modular webhooks
Receive real-time notifications directly to your server. Every time an email is delivered, opened, bounces, or a link is clicked.
[Learn more](https://resend.com/docs/dashboard/webhooks/introduction)
### Write using a delightful editor
A modern editor that makes it easy for anyone to write, format, and send emails.
Visually build your email and change the design by adding custom styles.
Styles
Weekly Acme Newsletter
a day ago
Test
Send
Fromyour.name@acme.com
To Newsletter Subscribers
SubjectWeekly Newsletter
### Go beyond editing
Group and control your contacts in a simple and intuitive way.
Straightforward analytics and reporting tools that will help you send better emails.
### Contact management
Import your list in minutes, regardless the size of your audience. Get full visibility of each contact and their personal attributes.
[Learn more](https://resend.com/features/audiences)
### Broadcast analytics
Unlock powerful insights and understand exactly how your audience is interacting with your broadcast emails.
[Learn more](https://resend.com/features/broadcasts)
### Develop emails using React
Create beautiful templates without having to deal with
layouts and HTML.
Powered by react-email, our open source component library.
### Reach humans, not spam folders
##### Proactive blocklist tracking
Be the first to know if your domain is added to a such as those offered by with removal requests generated by Resend.
##### Faster time to inbox
Send emails from the region closest to your users. Reduce delivery latency with North American, South American, European, and Asian regions.
##### Build confidence with BIMI
Showcase your logo and company branding with . Receive guidance to obtain a \- the email equivalent of a checkmark on social media.
##### Managed dedicated IPs
Get a fully managed dedicated IP that automatically warms up and autoscales based on your sending volume, no waiting period.
##### Dynamic suppression list
Prevent repeated sending to recipients who no longer want your email and comply with standards like the and others.
##### IP and domain monitoring
Monitor your DNS configuration for any errors or regressions. Be notified of any changes that could hinder your deliverability.
##### Verify DNS records
Protect your reputation by verifying your identity as a legitimate sender. Secure your email communication using and .
##### Battle-tested infrastructure
Rely on a platform of reputable IP's used by trustworthy senders with distributed workloads across different IP pools.
##### Prevent spoofing with DMARC
Avoid impersonation by creating policies and instructing inbox providers on how to treat unauthenticated email.
> Resend is transforming email for developers. Simple interface, easy integrations, handy templates. What else could we ask for.
Guillermo Rauch
CEO at Vercel
[Send with Next.js](https://resend.com/docs/send-with-nextjs)
### Everything in your control
All the features you need to manage your email sending, troubleshoot with
detailed logs, and protect your domain reputation – without the friction.
### Beyond expectations
Resend is driving remarkable developer experiences that enable success
stories, empower businesses, and fuel growth across industries and individuals.
### Email reimagined.
Available today.
---
## Humans · Resend
· 69 words
### Humans
behind Resend
We're a team of 50 makers who believes in
building great software that inspires others.
* * *
#### Team emeriti
A special thanks to some former team members
who have made valuable contributions.
- [
## Krithika
San Diego, USA
](https://resend.com/humans/krithika-yetchina)
- [
## James
Austin, USA
](https://resend.com/humans/james-martinez)
- [
## Pedro
São Paulo, Brazil
](https://resend.com/humans/pedro-gomes)
- [
## Caroline
San Francisco, USA
](https://resend.com/humans/caroline-moreschi)
---
## Audiences · Manage contacts easily · Resend
· 174 words
Import lists
### Add contacts
any way you like
Import your list in minutes, regardless the size of your audience.
Get full visibility of each contact and their personal attributes.
> Resend Audiences made it very easy for us. The accurate reporting and clean interface let us focus on the important thing: communicating with our users.
Steven Chacko
Co-Founder at Hike Medical
[Read story](https://resend.com/customers/hike-medical)
Unsubscribe handling
### View and control
unsubscribe status
It is important to give your contacts the ability to unsubscribe from emails.
Resend gives you the ability to include unsubscribe links and manages that flow for you.
Code integration
### Integrate your
audience with code
Add the logic to create, update, unsubscribe,
and remove contacts directly into your application.
import { Resend } from 'resend';
const resend \= new Resend('re\_xxxxxxxxx');
await resend.contacts.create({
email: 'steve.wozniak@gmail.com',
firstName: 'Steve',
lastName: 'Wozniak',
unsubscribed: false,
properties: {
company\_name: 'Acme Corp',
},
});
### Start sending in minutes
Resend delivers mission-critical emails for some
of the fastest growing teams.
[Sign up for free](https://resend.com/signup)
---
## Introduction - Resend
· 41 words
A collection of answers to frequently asked questions.
### Domains & Verification
### DNS Guides
Step-by-step instructions for verifying your domain with popular DNS providers.
### Deliverability
### Sending
### Tutorials
### Troubleshooting
### AI Tools
### Account Management
### Testing
---
## Blog · Resend
· 2026-06-03 · 2892 words
- [
## The Email Verification API
](https://resend.com/blog/email-verification-api)
- [
## How APRF Helps You Understand Your Email Reputation
](https://resend.com/blog/what-is-aprf)
- [
## Welcoming Laura Beatris, our new Software Engineer
](https://resend.com/blog/welcoming-laura-beatris)
·Aug 19, 2026
- [
## Welcoming Fabio Kubo, our new Software Engineer
](https://resend.com/blog/welcoming-fabio-kubo)
·Aug 12, 2026
- [
## Welcoming Mateus Resende, our new Software Engineer
](https://resend.com/blog/welcoming-mateus-resende)
·Aug 12, 2026
- [
## How to Show Your Logo in Apple Mail
](https://resend.com/blog/apple-branded-mail)
- [
## Welcoming Phil Nash, our new Developer Experience Engineer
](https://resend.com/blog/welcoming-phil-nash)
·Jul 30, 2026
- [
## The New DMARC is Here
](https://resend.com/blog/the-new-dmarc-is-here)
- [
## Welcoming Matt Gilbert, our new Data Analyst
](https://resend.com/blog/welcoming-matt-gilbert)
·Jul 9, 2026
- [
## Sunsetting new.email
](https://resend.com/blog/sunsetting-new-email)
- [
## Engineering a Vercel Chat Adapter
](https://resend.com/blog/engineering-a-vercel-chat-adapter)
- [
## Welcoming Kelsey Mills, our new Operations Generalist
](https://resend.com/blog/welcoming-kelsey-mills)
·Jun 4, 2026
- [
## 3,000,000 users
](https://resend.com/blog/3-million-users)
- [
## Welcoming Ben Anderson, our new Ops Generalist
](https://resend.com/blog/welcoming-ben-anderson)
·Jun 2, 2026
- [
## 6 Tips for Accessible Emails
](https://resend.com/blog/6-tips-for-accessible-emails)
·May 28, 2026
- [
## Welcoming Manoel do Amaral, our new Brand Designer
](https://resend.com/blog/welcoming-manoel-doamaral)
·May 22, 2026
- [
## Welcoming Michael Vaz, our new Customer Success Engineer
](https://resend.com/blog/welcoming-michael-vaz)
·May 21, 2026
- [
## Six Steps to Improve Your Sender Reputation
](https://resend.com/blog/6-steps-to-improve-your-sender-reputation-score)
- [
## Welcoming Tatira Andrade, our new Executive Assistant
](https://resend.com/blog/welcoming-tatira-andrade)
·May 20, 2026
- [
## Welcoming Pedro Ivo Hudson, our new Design Engineer
](https://resend.com/blog/welcoming-pedro-ivo-hudson)
·May 1, 2026
- [
## Welcoming Diel Duarte, our new Open source Engineer
](https://resend.com/blog/welcoming-diel-duarte)
·Apr 30, 2026
- [
## Launch Week 6: Wrap Up
](https://resend.com/blog/launch-week-6-wrap-up)
- [
## Resend Forward: A Conference about Craft
](https://resend.com/blog/resend-forward)
- [](https://resend.com/humans/christina-martinez)
- [](https://resend.com/humans/zeno-rocha)
- [](https://resend.com/humans/giovana-yahiro)
- +4
·Apr 18, 2026
- [
## React Email 6.0
](https://resend.com/blog/react-email-6)
- [](https://resend.com/humans/danilo-woznica)
- [](https://resend.com/humans/gabriel-miranda)
- [](https://resend.com/humans/joao-melo)
- +1
·Apr 17, 2026
- [
## Custom Tracking Domains
](https://resend.com/blog/introducing-custom-tracking-domain)
- [](https://resend.com/humans/anna-ward)
- [](https://resend.com/humans/rehan-van-der-merwe)
- [](https://resend.com/humans/mateusz-wos)
- +1
·Apr 16, 2026
- [
## Resend CLI 2.0
](https://resend.com/blog/resend-cli-2)
·Apr 15, 2026
- [
## AI Email Editor
](https://resend.com/blog/ai-email-editor)
- [](https://resend.com/humans/danilo-woznica)
- [](https://resend.com/humans/joao-melo)
- [](https://resend.com/humans/gabriel-miranda)
- +1
·Apr 14, 2026
- [
## Introducing Automations
](https://resend.com/blog/introducing-automations)
- [](https://resend.com/humans/carolina-josephik)
- [](https://resend.com/humans/danilo-campos)
- [](https://resend.com/humans/isabella-aquino)
- +3
·Apr 13, 2026
- [
## Welcoming Ahmed Tolba, our new SRE Engineer
](https://resend.com/blog/welcoming-ahmed-tolba)
·Apr 8, 2026
- [
## Welcoming Aneil Singh, our new Founding Account Executive
](https://resend.com/blog/welcoming-aneil-singh)
·Apr 3, 2026
- [
## Welcoming Lucas Motta, our new Software Engineer
](https://resend.com/blog/welcoming-lucas-motta)
·Apr 2, 2026
- [
## Welcoming Trey Knowles, our new Founding Account Executive
](https://resend.com/blog/welcoming-trey-knowles)
·Mar 25, 2026
- [
## Welcoming Anxhela Carciu, our new SRE Engineer
](https://resend.com/blog/welcoming-anxhela-carciu)
·Mar 13, 2026
- [
## Introducing DMARC Analyzer
](https://resend.com/blog/introducing-dmarc-analyzer)
- [
## Welcoming Evan Thibodeau, our new Customer Success Engineer
](https://resend.com/blog/welcoming-evan-thibodeau)
·Mar 6, 2026
- [
## Welcoming Derich Pacheco, our new Software Engineer
](https://resend.com/blog/welcoming-derich-pacheco)
·Mar 4, 2026
- [
## Welcoming Alec Ventura, our new Data Engineer
](https://resend.com/blog/welcoming-alec-ventura)
·Feb 27, 2026
- [
## Welcoming Felipe Freitag, our new Software Engineer
](https://resend.com/blog/welcoming-felipe-freitag)
·Feb 25, 2026
- [
## Welcoming Mateusz Wos, our new Software Engineer
](https://resend.com/blog/welcoming-mateusz-wos)
·Feb 18, 2026
- [
## Incident report for February 15, 2026
](https://resend.com/blog/incident-report-for-february-15-2026)
·Feb 16, 2026
- [
## Email automation for OpenClaw
](https://resend.com/blog/email-automation-for-openclaw-using-resend)
- [
## How to Create a DevTools Agent Skill
](https://resend.com/blog/how-to-create-a-devtools-agent-skill)
- [
## Introducing Email Skills
](https://resend.com/blog/introducing-email-skills)
- [
## Why You Should Embrace the Promotions Tab
](https://resend.com/blog/why-you-should-embrace-promotions-tab-gmail)
- [
## Slater Smith, our new Customer Success Engineer
](https://resend.com/blog/welcoming-slater-smith)
·Jan 14, 2026
- [
## Do You Need a Warmup Service?
](https://resend.com/blog/do-you-need-a-warmup-service)
- [
## Welcoming Zá Scalon, our new Brand Designer
](https://resend.com/blog/welcoming-za-scalon)
·Jan 7, 2026
- [
## How Replit Built Effortless Email Sending Features
](https://resend.com/blog/how-replit-built-effortless-email-sending-features)
- [
## 1,000,000 users
](https://resend.com/blog/1-million-users)
- [
## Top 10 new features in 2025
](https://resend.com/blog/new-features-in-2025)
- [
## Welcoming Danilo Campos, our new Design Engineer
](https://resend.com/blog/welcoming-danilo-campos)
·Dec 8, 2025
- [
## How Dub Uses Webhooks to Power Features
](https://resend.com/blog/how-dub-uses-webhooks-to-power-features)
- [
## Incident report for November 18, 2025
](https://resend.com/blog/incident-report-for-november-18-2025)
·Nov 18, 2025
- [
## Resend Forward 5: Wrap Up
](https://resend.com/blog/resend-forward-5-wrap-up)
- [
## One More (AI) Thing
](https://resend.com/blog/one-more-ai-thing)
·Nov 8, 2025
- [
## React Email 5.0
](https://resend.com/blog/react-email-5)
·Nov 7, 2025
- [
## Unsubscribe Topics
](https://resend.com/blog/unsubscribe-topics)
- [](https://resend.com/humans/alexandre-cisneiros)
- [](https://resend.com/humans/carolina-josephik)
- [](https://resend.com/humans/cassio-zen)
- +1
·Nov 6, 2025
- [
## New Contacts Experience
](https://resend.com/blog/new-contacts-experience)
- [](https://resend.com/humans/alexandre-cisneiros)
- [](https://resend.com/humans/cassio-zen)
- [](https://resend.com/humans/danilo-woznica)
- +2
·Nov 5, 2025
- [
## Introducing Templates
](https://resend.com/blog/introducing-templates)
- [](https://resend.com/humans/carolina-josephik)
- [](https://resend.com/humans/giovana-yahiro)
- [](https://resend.com/humans/isabella-aquino)
- +2
·Nov 4, 2025
- [
## Inbound Emails
](https://resend.com/blog/inbound-emails)
- [](https://resend.com/humans/lucas-costa)
- [](https://resend.com/humans/lucas-vieira)
- [](https://resend.com/humans/giovana-yahiro)
- +6
·Nov 3, 2025
- [
## $3M to Make Email Safer
](https://resend.com/blog/3-million-to-make-email-safer)
- [
## Hacktoberfest 2025
](https://resend.com/blog/hacktoberfest-2025)
- [
## Four Ways to Hurt Your Sender Reputation
](https://resend.com/blog/four-ways-to-hurt-your-sender-reputation)
[Pauline Chin](https://resend.com/humans/pauline-chin)·Sep 24, 2025
- [
## Resend MCP Hackathon
](https://resend.com/blog/resend-mcp-hackathon)
·Sep 17, 2025
- [
## Welcoming Christina Martinez, our new Developer Experience Engineer
](https://resend.com/blog/welcoming-christina-martinez)
·Sep 15, 2025
- [
## How to read a DMARC report
](https://resend.com/blog/how-to-read-a-dmarc-report)
- [
## Welcoming Erin Levine, our new Chief of Staff
](https://resend.com/blog/welcoming-erin-levine)
·Sep 10, 2025
- [
## How to Validate Form Inputs
](https://resend.com/blog/how-to-validate-form-inputs)
- [
## Engineering an AI App
](https://resend.com/blog/engineering-an-ai-app)
- [
## Welcoming Lucas da Costa, our new Software Engineer
](https://resend.com/blog/welcoming-lucas-da-costa)
·Aug 19, 2025
- [
## Welcoming Lucas Vieira, our new Software Engineer
](https://resend.com/blog/welcoming-lucas-vieira)
·Aug 19, 2025
- [
## Resend acquires Briefer
](https://resend.com/blog/resend-acquires-briefer)
·Aug 5, 2025
- [
## How Raycast Modernized their Email Sending
](https://resend.com/blog/how-raycast-modernized-their-email-sending)
·Jul 23, 2025
- [
## How to Get Email Consent
](https://resend.com/blog/how-to-properly-get-email-consent)
- [
## DMARC Policy Modes
](https://resend.com/blog/dmarc-policy-modes)
- [
## Welcoming Gabriel Miranda, our new Software Engineer
](https://resend.com/blog/welcoming-gabriel-miranda)
·Jul 9, 2025
- [
## Rebranding Resend
](https://resend.com/blog/rebranding-resend)
·Jul 1, 2025
- [
## The 7 Best Email Verification APIs for Developers
](https://resend.com/blog/best-email-verification-apis)
- [
## How DMARC Applies to Subdomains
](https://resend.com/blog/how-dmarc-applies-to-subdomains)
- [
## Welcoming Pedro Gomes, our new Software Engineer
](https://resend.com/blog/welcoming-pedro-gomes)
·Jun 13, 2025
- [
## Do You Need a Dedicated IP?
](https://resend.com/blog/do-you-need-a-dedicated-ip)
·Jun 4, 2025
- [
## The 6 best notification infrastructure services
](https://resend.com/blog/best-notification-infrastructure-services)
- [
## The Fixer
](https://resend.com/blog/the-fixer)
[Bu Kinoshita](https://resend.com/humans/bu-kinoshita)·May 29, 2025
- [
## Why Your Emails are Going to Spam
](https://resend.com/blog/why-your-emails-are-going-to-spam)
[Pauline Chin](https://resend.com/humans/pauline-chin)·May 21, 2025
- [
## Engineering Idempotency Keys
](https://resend.com/blog/engineering-idempotency-keys)
·May 7, 2025
- [
## Microsoft’s bulk sending requirements for 2025
](https://resend.com/blog/microsoft-bulk-sending-requirements-2025)
- [
## Welcoming Rehan van der Merwe, our new Devops Engineer
](https://resend.com/blog/welcoming-rehan-van-der-merwe)
·Apr 30, 2025
- [
## 400,000 users and beyond
](https://resend.com/blog/400-000-users-and-beyond)
- [
## Welcoming Cassio Zen, our new Software Engineer
](https://resend.com/blog/welcoming-cassio-zen)
·Apr 25, 2025
- [
## Resend acquires Mergent
](https://resend.com/blog/resend-acquires-mergent)
·Apr 23, 2025
- [
## How to warm up a new domain
](https://resend.com/blog/how-to-warm-up-a-new-domain)
- [
## Welcoming Carolina Josephik, our new Software Engineer
](https://resend.com/blog/welcoming-carolina-josephik)
·Apr 15, 2025
- [
## Launch Week: Behind the Scenes
](https://resend.com/blog/launch-week-behind-the-scenes)
- [
## Welcoming Isabella Aquino, our new Software Engineer
](https://resend.com/blog/welcoming-isabella-aquino)
·Apr 2, 2025
- [
## Resend Forward 4: Wrap Up
](https://resend.com/blog/resend-forward-4-wrap-up)
- [
## React Email 4.0
](https://resend.com/blog/react-email-4)
- [
## Multiplayer Editor
](https://resend.com/blog/multiplayer-editor)
- [
## Broadcast API
](https://resend.com/blog/broadcast-api)
·Mar 26, 2025
- [
## Multiple Teams
](https://resend.com/blog/multiple-teams)
- [
## new.email Public Launch
](https://resend.com/blog/new-email-public-launch)
- [
## Welcoming Anna Ward, our new Postmaster
](https://resend.com/blog/welcoming-anna-ward)
·Mar 18, 2025
- [
## How Gumroad Migrated 100M Emails to Resend
](https://resend.com/blog/how-gumroad-migrated-100m-emails-to-resend)
- [
## Welcoming João Melo, our new Software Engineer
](https://resend.com/blog/welcoming-joao-melo)
·Mar 12, 2025
- [
## Welcoming Jp Valery, our new Customer Success Engineer
](https://resend.com/blog/welcoming-jp-valery)
·Feb 26, 2025
- [
## What is AX (Agent Experience) and how to improve it
](https://resend.com/blog/agent-experience)
- [
## Welcoming Pauline Chin, our new Customer Success Engineer
](https://resend.com/blog/welcoming-pauline-chin)
·Feb 19, 2025
- [
## Introducing new.email
](https://resend.com/blog/introducing-new-email)
- [
## How we use Friction Logs to improve the product
](https://resend.com/blog/how-we-use-friction-logs-to-improve-the-product)
- [
## Top 10 Email Deliverability Tips
](https://resend.com/blog/top-10-email-deliverability-tips)
- [
## Welcoming Giovana Yahiro, our new Designer Engineer
](https://resend.com/blog/welcoming-giovana-yahiro)
·Jan 7, 2025
- [
## What BIMI's Changes Mean for Email
](https://resend.com/blog/email-changes-for-bimi)
- [
## Top 10 new features in 2024
](https://resend.com/blog/new-features-in-2024)
- [
## Design Engineering an X Component
](https://resend.com/blog/design-engineering-an-x-component)
- [
## Welcoming Alexandre Cisneiros, our new Software Engineer
](https://resend.com/blog/welcoming-alexandre-cisneiros)
·Dec 5, 2024
- [
## Resend raises $18M Series A
](https://resend.com/blog/series-a)
- [
## Welcoming Danilo Woznica, our new Designer Engineer
](https://resend.com/blog/welcoming-danilo-woznica)
·Nov 20, 2024
- [
## Reflections on my first Resend offsite
](https://resend.com/blog/reflections-on-my-first-resend-offsite)
- [
## Welcoming Chris Pennington, our new Developer Experience Engineer
](https://resend.com/blog/welcoming-chris-pennington)
·Oct 22, 2024
- [
## Introducing the Scale plan
](https://resend.com/blog/introducing-the-scale-plan)
- [
## Email changes coming to iOS 18
](https://resend.com/blog/email-changes-coming-to-ios-18)
- [
## How Vercel uses React Email for Next.js Conf
](https://resend.com/blog/how-vercel-uses-react-email-for-next-js-conf)
- [
## Resend's First Ops Offsite
](https://resend.com/blog/first-ops-offsite)
- [
## Resend Forward 3: Wrap Up
](https://resend.com/blog/resend-forward-3-wrap-up)
- [
## Broadcast Schedule
](https://resend.com/blog/broadcast-schedule)
[Zeh Fernandes](https://resend.com/humans/zeh-fernandes)·Aug 25, 2024
- [
## React Email 3.0
](https://resend.com/blog/react-email-3)
- [
## Deliverability Insights
](https://resend.com/blog/deliverability-insights)
- [
## Introducing Marketing Analytics
](https://resend.com/blog/introducing-marketing-analytics)
[Bu Kinoshita](https://resend.com/humans/bu-kinoshita)·Aug 21, 2024
- [
## Vercel Integration
](https://resend.com/blog/vercel-integration)
[Vitor Capretz](https://resend.com/humans/vitor-capretz)·Aug 20, 2024
- [
## Introducing the Schedule Email API
](https://resend.com/blog/introducing-the-schedule-email-api)
- [
## Welcoming Brian Kerr, our new Customer Success Engineer
](https://resend.com/blog/welcoming-brian-kerr)
·Jul 30, 2024
- [
## Resend's journey to GDPR compliance
](https://resend.com/blog/gdpr)
- [
## Welcoming Felipe Volpone, our new Software Engineer
](https://resend.com/blog/welcoming-felipe-volpone)
·Jun 25, 2024
- [
## Resend named to Redpoint's InfraRed 100
](https://resend.com/blog/resend-named-to-redpoint-infra-red-100)
- [
## Welcoming Bruno Rubin, our new DevOps Engineer
](https://resend.com/blog/welcoming-bruno-rubin)
·May 1, 2024
- [
## What's next after 100,000 users
](https://resend.com/blog/what-is-next-after-100-000-users)
- [
## Resend is SOC 2 Type II compliant
](https://resend.com/blog/soc-2)
- [
## Incident report for February 21st, 2024
](https://resend.com/blog/incident-report-for-february-21-2024)
[Bu Kinoshita](https://resend.com/humans/bu-kinoshita)·Feb 22, 2024
- [
## Resend Forward: Wrap Up
](https://resend.com/blog/resend-forward-wrap-up)
- [
## Introducing Light Mode
](https://resend.com/blog/introducing-light-mode)
[Zeh Fernandes](https://resend.com/humans/zeh-fernandes)·Jan 20, 2024
- [
## React Email 2.0
](https://resend.com/blog/react-email-2)
- [
## Introducing the Batch Emails API
](https://resend.com/blog/introducing-the-batch-emails-api)
[Vitor Capretz](https://resend.com/humans/vitor-capretz)·Jan 18, 2024
- [
## Improving Time to Inbox in Asia
](https://resend.com/blog/improving-time-to-inbox-in-asia)
- [
## Manage subscribers with Resend Audiences
](https://resend.com/blog/manage-subscribers-using-resend-audiences)
[Bu Kinoshita](https://resend.com/humans/bu-kinoshita)·Jan 16, 2024
- [
## Send Marketing Emails with Resend Broadcasts
](https://resend.com/blog/send-marketing-emails-with-resend-broadcasts)
[Zeh Fernandes](https://resend.com/humans/zeh-fernandes)·Jan 15, 2024
- [
## Incident report for January 10, 2024
](https://resend.com/blog/incident-report-for-january-10-2024)
- [
## Gmail and Yahoo’s bulk sending requirements for 2024
](https://resend.com/blog/gmail-and-yahoo-bulk-sending-requirements-for-2024)
- [
## Improved Performance for Tailwind Emails
](https://resend.com/blog/improved-performance-for-tailwind-emails)
- [
## Welcoming Krithika Yetchina, our new Customer Support Engineer
](https://resend.com/blog/welcoming-krithika-yetchina)
·Nov 22, 2023
- [
## How to send emails using Bun
](https://resend.com/blog/how-to-send-emails-using-bun)
[Vitor Capretz](https://resend.com/humans/vitor-capretz)·Sep 20, 2023
- [
## Welcoming Haison Ohara, our new Developer Success Engineer
](https://resend.com/blog/welcoming-haison-ohara)
- [
## Welcoming Vitor Capretz, our new Software Engineer
](https://resend.com/blog/welcoming-vitor-capretz)
·Sep 7, 2023
- [
## Email Authentication: A Developer's Guide
](https://resend.com/blog/email-authentication-a-developers-guide)
- [
## How to configure Supabase to send emails from your domain
](https://resend.com/blog/how-to-configure-supabase-to-send-emails-from-your-domain)
- [
## Why SMTP still matters today
](https://resend.com/blog/why-smtp-still-matters-today)
- [
## Resend raises $3M
](https://resend.com/blog/resend-raises-3m-seed-round)
- [
## New Free Tier
](https://resend.com/blog/new-free-tier)
- [
## Welcoming Zeh Fernandes, our new Product Designer
](https://resend.com/blog/welcoming-zeh-fernandes)
·May 16, 2023
- [
## Launch Week 1: Wrap Up
](https://resend.com/blog/launch-week-1-wrap-up)
- [
## Send emails using React and Tailwind CSS
](https://resend.com/blog/tailwind-with-react-email)
- [
## Open and Click Tracking
](https://resend.com/blog/open-and-click-tracking)
- [
## Supercharge Sending with Integrations
](https://resend.com/blog/new-integrations)
- [
## New Domain Verification Experience
](https://resend.com/blog/new-domain-verification-experience)
- [
## Capture email events with Webhooks
](https://resend.com/blog/webhooks)
- [
## Introducing Managed Dedicated IPs
](https://resend.com/blog/dedicated-ips)
- [
## Faster Email Delivery with Multi-Region
](https://resend.com/blog/multi-region)
- [
## Lessons learned from growing a 6,338 people waitlist in 7 weeks
](https://resend.com/blog/lessons-learned-from-growing-a-waitlist)
- [
## Why I spent $25,000 on a domain (or how to pick a startup name)
](https://resend.com/blog/how-to-pick-a-startup-name)
- [
## Resend + Y Combinator
](https://resend.com/blog/y-combinator)
- [
## Introducing Resend
](https://resend.com/blog/introducing-resend)
---
## Automations · Build event-driven email flows · Resend
· 209 words
import { Resend } from 'resend';
const resend \= new Resend('re\_xxxxxxxxx');
const { data, error } \= await resend.events.send({
event: 'user.created',
email: 'steve.wozniak@gmail.com',
payload: {
plan: 'pro',
},
});
Custom Events
### Trigger actions
via custom events
Define events with strongly typed schemas and trigger them via API. Whether it's a user sign up, a payment failing, or an order shipping. Your data, your events.
Control the flow
### Orchestrate every step of
your workflow
Build multi-step workflows with precise timing and logic.
Decide when emails go out, who gets them, and what happens next.
Observability
### Granular visibility
of all runs and steps
Every automation run is saved, so you can understand what
happened at each step.
> Resend Automations turned our hand-built, tangled setup into a clean, reliable way to send personalized, multi-day welcome sequences to new users.
Pierson Marks
Founder & CEO of Jellypod
Easy to use
### Start automating
your emails
Set up your first automation in simple steps. Streamline
your email workflows and engage effortlessly.
- Up to 10,000 runs per month
- Unlimited automations
- Unlimited steps
- No credit card required
### Start sending in minutes
Resend delivers mission-critical emails for some
of the fastest growing teams.
[Sign up for free](https://resend.com/signup)
---
## Pricing · Resend
· 273 words
Start for free and scale as you grow.
### Add-ons
### Domains - $20 / mo
Your plan already comes with domains, but if you send from a separate one for each customer or brand, that number runs out quickly. This adds 100 more on top of it. Available on Pro and Scale, and you can add or remove it yourself whenever you need to. On Enterprise, your domain limit is set in your contract.
### Dedicated IPs - $30 / mo
Available to customers exceeding 3,000 emails sent per day on the Scale plan. We take great care to maintain good-standing shared IP's, but for some high-volume senders, you can't leave anything up to chance. We will warmup, monitor, and autoscale it based on your utilization so you can focus on one thing, sending.
### Sending & receiving
Free
Pro
Scale
Enterprise
100
No limit
No limit
No limit
### Deliverability & reliability
Free
Pro
Scale
Enterprise
3
10
1,000
Flexible
–
With add-on
With add-on
Flexible
–
–
With add-on
With add-on
–
–
30 days
30 days
30 days
Flexible
1 endpoint
5 endpoints
10 endpoints
Flexible
All events
All events
All events
All events
### Security & privacy
Free
Pro
Scale
Enterprise
### Customer support
Free
Pro
Scale
Enterprise
–
–
–
–
–
### AI credits
Free
Pro
Scale
Enterprise
5
100
500
Flexible
Trusted by
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
### Start sending in minutes
Resend delivers mission-critical emails for some
of the fastest growing teams.
[Sign up for free](https://resend.com/signup)
---
## Welcoming Laura Beatris, our new Software Engineer
· 2026-08-19 · 649 words
We're excited to share that [Laura Beatris](https://resend.com/humans/laura-beatris) is joining the Resend team as a Software Engineer.
Laura is an engineer who loves building tools for developers. She previously worked at Clerk and WorkOS, shipping authentication products with an eye for developer experience.
She's also given talks and podcasts about React, TypeScript, and learning in the open. Here's our favorite talk from her: [The Future of Authentication in React Native](https://www.youtube.com/watch?v=Dzsp3aWkVtQ&pp=ygUNbGF1cmEgYmVhdHJpcw%3D%3D).
### [More about Laura](#more-about-laura)
**How did you get into software?**
I got into computers pretty early. I was around 7, and my older brother was really into videogames, so we played together all the time. Ragnarok and Grand Chase were our favorite ones!
Ragnarok's screenshot
When I was finishing high school, Florianópolis started being called the Silicon Valley of Brazil. I had always wanted to live abroad, get to know a new culture, and work with software engineering in English. Seeing tech grow in my own city made that feel possible.
Instead of studying for university entrance exams, I used that time to learn Python from free tutorials. After high school I started a technical degree in Analysis and Systems Development, and I began applying for internships in my first semester. It was one rejection after another, which pushed me to build projects and study beyond the curriculum. That path eventually took me to Amsterdam in 2021.
My first year in Amsterdam
**What does your desktop/home screen look like?**
I keep my setup as minimal as possible so nothing distracts me. Native macOS wallpapers with nature views, dock icons as small as they'll go, and a weather widget to check what's going on in my city.
Laura's desktop
**Why are you at Resend?**
I've always wanted to work on products where the details matter, and I started my career by learning in public. Resend does both. I learned by building things and then sharing them, and that's a big part of why I wanted to be here. It's also a new problem space for me, as I keep improving my taste around developer experience.
**Where do you find #inspiration?**
I find a lot of inspiration in music, movies, and art. Van Gogh and Monet are my favorite artists. Their attention to detail and the craft they put into their work helped me develop taste over the years.
Van Gogh's museum
One of my biggest inspirations for hard work is Ayrton Senna. He kept going after things people thought were impossible.
Laura's shelf
**If you weren't programming, what would you be doing?**
I'd be a videographer or a photographer. Going out and capturing moments is one of my favorite ways of making art, and of being present in the world. Getting to fully focus on that would be amazing.
Out taking photos
**Favorite tool?**
Raycast. I use it all day to search, switch apps, and automate the small stuff.
**Favorite hotkey?**
Still deciding on this one.
**Favorite place to visit?**
Bariloche, Argentina.
It's where I saw snow for the first time. The views of Patagonia are breathtaking. I still can't believe we have that kind of nature in South America. The city in winter is so quiet. It just feels peaceful.
Bariloche
**Advice for ambitious software engineers?**
Learn → Create → Teach.
From my first job as a junior to now, I never really found a way of learning that I could keep using. There's always a new tool, a new pattern, a new thing everyone is talking about.
The workflow that finally stuck is simple: learn something, build with it, then teach it. Teaching is the part that makes the knowledge stay. You communicate better, you help other people grow, and you realize you understood it more deeply than you thought.
I also wish I'd started going to meetups and conferences much earlier. I kept waiting until I felt ready enough to be there, and that just made me wait.
---
## Send emails with Node.js - Resend
· 58 words
Learn how to send your first email using the Resend Node.js SDK.
Use this pre-built prompt to get started faster.
### Prerequisites
Before you start, you’ll need:
- A Resend [API key](https://resend.com/docs/create-an-api-key)
- A [verified domain](https://resend.com/docs/add-a-domain)
### Guide
1
2
3
### Examples
Was this page helpful?
[
AI onboarding
Previous
](https://resend.com/docs/ai-onboarding)[
Send emails with Next.js
Next
](https://resend.com/docs/send-with-nextjs)
---
## How APRF Helps You Understand Your Email Reputation
· 2026-08-20 · 932 words
There is a new standard for email deliverability feedback that could help you better understand your sending reputation. It's backed by contributors from Comcast, Google, and Iterable.
It's called _Aggregate Performance Reporting_ (APRF) and is [currently a draft specification](https://datatracker.ietf.org/doc/draft-brotman-aggregate-performance-reporting/). If it is adopted it should prove key to understanding how your emails are performing with real users.
### [What is APRF?](#what-is-aprf)
APRF is an aggregated feedback mechanism that tells senders two things:
1. **Classification:** where do mailbox providers place your emails
2. **Engagement:** how real users interact with your emails
Classification details whether your emails arrive in the inbox, the spam folder, or other inbox specific folders like the [Promotions tab](https://resend.com/blog/why-you-should-embrace-promotions-tab-gmail). Engagement is recorded as positive, negative, or neutral.
User engagement
The spec doesn't define the user actions that are counted as positive, negative, or neutral as they could be considered "secret sauce" for a mailbox provider, but it does provide the following suggestions:
- positive: opening, clicking, or removing from the spam folder.
- negative: sending to spam, deleting without opening, unsubscribing.
- neutral: forwarding, filing into a normal folder.
Mailbox providers that support APRF will deliver a daily email containing a JSON report to an address that you [configure with DNS records](#how-do-you-set-up-aprf).
If you're already using [DMARC Reporting](https://resend.com/blog/how-to-read-a-dmarc-report), you're familiar with this type of reporting mechanism. APRF reports are similar but focus on classification and engagement.
### [An example report](#an-example-report)
Reports are JSON documents that look like this:
The report contains two basic sections:
- `header`: details about the mailbox provider that sent the report
- `body`: data for the reporting time period
The body further breaks into two sections:
1. `classification`: where the mailbox provider placed your emails
In the sample report, 100 emails landed in spam ("unwanted") and the rest were successfully delivered to the inbox.
The spec suggests that these numbers are buckets defined by the provider and that the upper bound for the buckets is used as the value. In this example, if it says 100,000 emails landed in the inbox, that's the maximum figure it could be. The real number would fall somewhere below 100,000 but above the bucket below, which could be at 50,000. It's intentionally inaccurate, but still useful as a gauge for your email deliverability over time.
2. `engagement`: what real users did with your emails
These signals are also bucketed values, showing whether users took positive, negative, or neutral actions with emails. As discussed earlier, the spec doesn't define what those actions mean, but suggests examples as a good start.
**Provider-specific details**
For each of the classification and engagement sections, the provider can add information about the buckets and what they mean in the header's `extra_info` section.
**Key takeaways**
In general, if your emails are classified as "inbox" and getting mostly positive actions, you are doing well. If they are classified as "unwanted" and receiving negative actions, then there is work to do to protect your domain's reputation.
For more on the data and detail you can get from APRF reports check out SH Consulting's report on [setting up APRF for more than 100 domains](https://www.sh.consulting/blog/aprf-aggregate-performance-reporting-deployment-guide).
### [How do you set up APRF?](#how-do-you-set-up-aprf)
APRF reports are sent to an email address that you configure with DNS.
In order to receive APRF reports, set up a DNS `TXT` record. The record name is derived from the DKIM signature used to sign your emails. The spec offers this example:
The name of the TXT record is then generated from the `s=` and `d=` sections of the signature using this template: `._aprf._domainkey.`. With the example signature above, the TXT record would be named `sel1._aprf._domainkey.foo.example.org`.
The content of the TXT record should consist of a version and the address the report will be sent to, e.g. `v=APRFv1;rua=mailto:reports@example.org;`.
You can also add an `sdi` attribute which stands for "Signer-Defined Identifier". This defines a header name that will be used to segment the data in the report and a separator that will allow you to drill down into more fine-grained segments.
With `sdi` included, your TXT record might look like:
You can then include a `Segmentation` header in your email like `Segmentation:BusinessName^Region^Campaign`. The `^` character is used to split the segmentation options and the daily reports will then provide details for the segments.
If you sent one email with the `Segmentation` header `BusinessName^Marketing` and another with the header `BusinessName^Transactional`, then for supporting mailboxes, your reports would include sections in the body for both segments:
Segmenting the results like this is a useful addition and can help you to go deeper into the analysis, from comparing transactional and marketing emails to examining specific marketing campaigns.
### [What this means for you](#what-this-means-for-you)
The reporting prioritizes bulk senders and provides an overall picture of the reception for your sending.
As of writing, APRF is an [Internet-Draft specification](https://www.ietf.org/participate/ids/); it hasn't yet been adopted by an IETF working group. Comcast is already sending out APRF reports, however, so there is a live implementation and hope for more. While Google is also an author of this specification, Gmail isn't delivering reports yet.
As the specification matures, that is something you could hope to see though. You can read more about the proposed standard in the [IETF draft specification](https://datatracker.ietf.org/doc/draft-brotman-aggregate-performance-reporting/).
**APRF is definitely worth watching.** Receiving reports of how users engage with your emails directly from the mailbox provider is invaluable, even if it is intentionally fuzzy.
If you care about your email deliverability, getting these signals will help you to understand and maintain your reputation. While you wait for this to roll out further, we have plenty of other [tips to help improve your deliverability](https://resend.com/blog/top-10-email-deliverability-tips).
---
## Welcoming Fabio Kubo, our new Software Engineer
· 2026-08-12 · 553 words
Today, we're excited to share that [Fabio Kubo](https://resend.com/humans/fabio-kubo) is joining our software engineering team.
With over 10 years of experience, Kubo has helped scale products to millions of customers at companies like iFood and Nu. We're thrilled to have him bring that experience to help us scale Resend's platform even further.
### [More about Kubo](#more-about-kubo)
**How did you get into software?**
I got into software without really knowing what it was. As a kid, I loved playing games and messing around on the computer — so much that my dad had to format it a few times because of me.
Given that background, I knew I'd enjoy something computer-related, so I decided to take a technical computer science course in high school. That's where everything started.
**What does your desktop/home screen look like?**
Kubo's desktop
**Why are you at Resend?**
I first heard about Resend from someone who already worked here. What caught my attention right away was the product, how fast Resend was growing, and the technical challenges behind supporting that growth.
But when I looked deeper into the company, I found the handbook — and that's what really got me. I had never seen a company with a fully public handbook before. I really connected with the values, the culture, the way of working, and of course, the transparency.
**Where do you find #inspiration?**
I don't have just one source of inspiration. I like to draw a little from many different people. A philosophy teacher of mine once told me, "Everyone can teach you something." I keep that in mind, building my own inspiration from small pieces of many unique people.
One thing that always helps me remember the purpose behind what I do is staying close to the people actually using the product I help build. Seeing a customer enjoy a new feature, and hearing their complaints, praise, and suggestions — that's what keeps me going.
**If you weren't programming, what would you be doing?**
I've always loved math and the exact sciences, so if it weren't for programming, I'd probably be in economics. I find it fascinating to understand a bit about macroeconomics and how it shapes people's everyday lives.
**Favorite tool?**
Notion. I couldn't live without it — I put everything I need to remember or do in there. It helps me free my mind and focus on the current task.
**Favorite hotkey?**
Multi-cursor editing in code editors. Yes, my favorite feature is slowly getting replaced by AI coding agents, but it still feels amazing when I get to change multiple lines at once with it.
**Favorite place to visit?**
At first, I was thinking about adding a photo from one of my trips, but after thinking more, I realized my favorite place lately has been Bosque dos Jequitibás, a park here in Campinas, Brazil.
It has everything I need to rest my mind — lots of trees, plenty of shade to walk and run even under Brazil's summer sun. I usually go at times when it's almost empty, which makes it the perfect place to reset.
Bosque dos Jequitibás
**Advice for ambitious software engineers?**
The best skill you can practice is learning how to learn. Figure out which method works best for you. Also, understanding the underlying concepts will help you navigate new domains, technologies, and tools.
---
## Philosophy · Resend
· 2024-12-04 · 630 words
#### Make it for everyone.
Not every person lives in San Francisco.
Not every engineer has the same skill level.
Not every team uses the hottest framework.
We can't build something only for the wealthy users but also for users at the margins (think the 90th percentile) who may not be on the fastest computers, WiFi networks, or have access to the latest tech.
That's why we have a generous free tier.
That's why we have SDKs for all languages.
That's why we have docs for beginners.
That's why it must be fast.
* * *
#### Friction must be zero.
We only have one chance to make a first impression, so the onboarding experience should be flawless.
It can't ask for a credit card.
It can't have dozens of steps.
It can't require a "demo" or "call".
It can't be a two-day verification process.
If a developer's first attempt at using the product takes several hours, they won't be coming back.
They should be able to go from hello world to production in minutes.
* * *
#### Documentation is the product.
Most companies treat documentation as an afterthought, something you do later.
For us, documentation is not auxiliary to the product.
Documentation is the product.
It's one of the first things developers will interact with when they're learning, and it's the thing they'll keep coming back to as they integrate deeper.
This means we need to treat it as a first-class citizen. It needs CI/CD, it needs to be in-app, it needs to be up-to-date, and it needs a roadmap.
* * *
#### Uptime is like water.
Uptime is as essential for infrastructure as water is essential for life.
We can have the most beautiful product in the world, but if it's not online, then it's all for nothing.
Reliability is the foundation of everything we do, and every time there's a downtime, we lose trust.
At the end of the day, we're providing infrastructure, just like water, energy, and transportation. Would you drink water that is only treated 99% of the time?
* * *
#### Predictable by design.
The output of the product should be credible, consistent, and predictable
Our platform is used by thousands of people in thousands of different ways. So, we must respect the contracts and interfaces we have with users. Updates should not result in surprises.
The response objects shouldn't change without notice. The error codes should follow the same structure. The API should be backwards compatible.
* * *
#### It must be fast.
When you load a page, when you visit the dashboard, when you make an API call, it can't be slow.
We need to always be decreasing response times, and improving performance. We should be constantly asking ourselves, "How can we make this faster?"
When in doubt, do what's faster for the user even if it means making it harder for us to build, test, and maintain.
* * *
#### No detail is too small.
For Resend to make an impact, it can't be just a little bit better than what's available out there. It needs to be an order of magnitude better.
The way to do that is by obsessing over every detail no matter how small. We believe that the sum of all the small details is what makes something special.
That's why we're willing to spend more time on something that may not be noticed by most people but will be truly appreciated by the right people.
### Read more
- [
## Resend raises $18M Series A
](https://resend.com/blog/series-a)
Dec 4, 2024
- [
## Resend + Y Combinator
](https://resend.com/blog/y-combinator)
Feb 1, 2023
- [
## Introducing Resend
](https://resend.com/blog/introducing-resend)
Jan 4, 2023
---
## The Email Verification API
· 2026-08-25 · 813 words
Whenever you collect an email address it is best practice to verify that the person who provided it actually owns it. It's all part of [getting email consent to send emails](https://resend.com/blog/how-to-properly-get-email-consent).
The [Email Verification API](https://github.com/WICG/email-verification) is a new proposal to make it easier by performing email verification directly within the browser.
### [Improving email verification](#improving-email-verification)
When a user enters an email address in a form online, it's common practice to verify their email by sending a one-time password (OTP) or magic link. The user leaves the webpage, opens their inbox, and copies a code or clicks a link.
This **adds friction**, breaks the user's flow and risks **losing their attention**.
When a user's email address can be verified by the browser and your application, **they never have to leave**, making registration or subscription a much smoother journey.
The proposed flow offers more than a better user experience. If the email address is verified, you can be more confident that it belongs to the user in question and reduce bounces caused by invalid or mistyped addresses. Both of these features help **protect your sender reputation**.
At the time of writing, this API is in the **proposal stage**. The browser API is only supported by Chrome via an [origin trial](https://developer.chrome.com/docs/web-platform/origin-trials) and mailbox verification is only supported by Gmail. It's worth experimenting with it now as a progressive enhancement.
There are other [email verification APIs](https://resend.com/blog/best-email-verification-apis) that verify syntax, MX records, and SMTP servers for an email address before you try sending to it. You might consider using one of those to verify an email address where this API isn't available.
### [How does the Email Verification API work?](#how-does-the-email-verification-api-work)
The API has a few different parties involved: the user, the browser, the mailbox provider (known as the issuer), and your server (the verifier). Here's a quick and simple version of how it all works together:
- The user logs into their mailbox provider and the mailbox registers that with the browser.
- Later, the user enters their email address into a form on your site.
- The browser checks to see if that email address is associated with the logged-in user.
- If they are, the browser and the mailbox provider create a token together and add it to a hidden input in the form.
- When the user submits the form the server receives the email address and the token.
- Verifying the token validates that the email address belongs to that user.
If you want to know exactly how the tokens are created and verified, I recommend reading through [this introduction to the Email Verification Protocol](https://developer.chrome.com/blog/email-verification-protocol-origin-trial).
To the user, the experience looks like this.
Let's look at how to implement the API so you can start verifying email addresses yourself.
### [The front-end](#the-front-end)
We'll start with the HTML form. The email `` needs to be of type "email" with the `autocomplete` attribute set to "email" as well.
You also need to provide a hidden input with the `autocomplete` attribute of "email-verification-token" that has a random nonce.
A [nonce](https://en.wikipedia.org/wiki/Cryptographic_nonce) is an arbitrary value that is used only once during a cryptographic communication to ensure each session is unique.
To create a nonce, generate a random string. In Node.js, for example, you can use the `randomUUID` function from the `node:crypto` standard library.
Bind this nonce to the user session so that you can use it later to help verify the token. Then add it as the `nonce` attribute on the hidden input.
That's all the front-end code required. Everything else happens between the browser, the issuer, and your server.
### [Verifying a token](#verifying-a-token)
The process of verifying the token is quite involved, requiring parsing, DNS and network lookups, and verifying the token signatures.
If your server is written in JavaScript, I built an [npm package to perform the verification](https://github.com/philnash/email-verification-api) for you. You can install it with:
And use it like so:
In this snippet, the `audience` is your site's origin, the `email` and the `token` come from the submitted form, and the `nonce` is retrieved from the session.
There is a full [example Next.js application](https://github.com/philnash/email-verification-api/tree/main/example) which shows you how it all works together.
You can try [the example app](https://verifyemails.vercel.app/) for yourself.
### [Better email verification is better for everyone](#better-email-verification-is-better-for-everyone)
I really like this API for two reasons.
**For the user**, there's no more heading off to their inbox to verify their email when they are just trying to get something done, and they don't have to change their behavior at all.
**For the application**, verifying emails helps you avoid hard bounces for email addresses that don't exist and ensures that the user really owns the email address.
If you want to follow the progress of this proposal, star the [repository on GitHub](https://github.com/WICG/email-verification) and follow the [updates on the Chrome for developers blog](https://developer.chrome.com/blog/email-verification-august-2026). If you want to implement it in your own application, check out the [email-verification-api repository](https://github.com/philnash/email-verification-api).
---