Running Resend?

Resend hitting spam or bounces piling up? We clear the backlog.

Resend is a modern email API with an excellent developer experience, which does not mean a mailbox provider will deliver a message you send. We work through SPF, DKIM, DMARC, the sending reputation of the IP pool, bounce handling and the React Email templates that look right in the preview and wrong in Outlook, and leave inbox placement measurable.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

resend-send.log

still broken

What it is

Resend at a glance

Resend is a transactional email API launched in 2023 by Zeno Rocha and Bu Kinoshita, built around React Email, a component library for writing emails in JSX that compiles to the HTML every mailbox expects. The platform covers transactional sending, broadcasts, webhooks, domain verification and a pleasant dashboard that does not look like it was last touched in 2012.

The developer experience is the selling point: an SDK that works the way you expect, templates you can keep in the same repo as the product, and a free tier that is genuinely usable. Deliverability, which is the actual job of sending email, depends on the usual set of DNS records, sender reputation and recipient engagement, none of which a slick SDK can shortcut. Most teams that come to us on Resend have a sending problem, not a Resend problem.

Type
Transactional email API with React Email templates
First released
2023
License
Proprietary SaaS, volume-based pricing with a free tier
Maintained by
Resend, Inc.
Typically used for
Transactional email, product notifications, verification messages, React Email broadcasts

The honest version

Resend pros and cons

No technology is all upside. This is where Resend earns its place and where it tends to cause trouble.

Where Resend is strong

  • React Email is a real improvementWriting emails as React components, previewing them in a browser and shipping the same JSX that the product team already understands is a genuine step up from hand-crafted table-based HTML.
  • The API is quick to integrateA single endpoint, a small SDK and sensible defaults get a transactional email live in minutes, with batching, scheduling and idempotency keys when you need them.
  • Webhooks that workDelivered, bounced, opened, clicked, complained, and delivery delayed all arrive as signed webhooks, so a product can react to bounces or complaints without polling.
  • Dashboards that help diagnoseMessage-level logs show the exact response from the recipient MTA, which is the information you actually need when a specific user did not receive a specific email.
  • Developer-friendly pricingA generous free tier and transparent per-message pricing without the step-function tier changes that plague older providers.
  • Broadcasts and transactional in one toolMarketing-style broadcasts and transactional mail live in the same account, which keeps domain reputation and unsubscribe handling consistent.

Where Resend bites

  • Deliverability is still your problemResend will not save a domain with bad SPF, broken DKIM or a long history of recipient complaints. A great API does not make a cold IP warm up any faster.
  • React Email renders differently per clientPreviewing in a browser is not the same as rendering in Outlook 2019 on Windows. Some components look fine in Gmail and ugly in corporate mail clients, and the testing story is manual.
  • Smaller suppression and compliance toolingCompared with SendGrid or SES, the suppression list handling, subaccount model and compliance tooling for big senders are leaner. It is a younger platform.
  • Volume ceilings existFor six or seven figure monthly volumes, dedicated IPs, pool management and carrier-grade throughput are still better served by established providers or SES on your own infrastructure.
  • Webhook retry semantics are strictSignatures expire after a short window, so a slow or queued consumer that reprocesses old webhooks has to ignore the staleness check carefully, not drop them.
  • Domain verification has DNS gotchasSPF lookup limits, DMARC alignment, BIMI and MX interaction catch teams who added Resend to a domain that already sends through Google Workspace or Microsoft 365.

Sound familiar?

Common Resend problems we fix

The Resend problems that bring people to us, and what you have once each one is fixed.

validation_error: 'from' must be a verified domain

Sends are rejected before leaving

A sending address on a domain that never finished DNS verification, or a verified subdomain being used with a bare apex in the From address. The error is clear once you know where to look.

Domains verified, sends accepted

DMARC: p=quarantine, 12% failures

Email is landing in spam at scale

DMARC alignment failing because the From domain and the Return-Path or DKIM-signing domain do not match, or because a forward chain is breaking SPF. We fix the alignment and the aggregate reports drop quickly.

Alignment clean, DMARC passing

DKIM signature verification failed

Some recipients reject messages

A DKIM key that was rotated at Resend but never updated in DNS, a TXT record that was wrapped with extra quotes, or a selector that was changed without the downstream knowing.

DKIM signed and verified

SPF: too many DNS lookups (11)

SPF exceeds the lookup limit

A domain that already includes Google Workspace, Microsoft 365, Mailgun and now Resend, with each include expanding to multiple lookups. The fix is flattening, not adding more.

SPF inside the ten-lookup limit

bounce webhook: 550 5.1.1 User unknown

Bounces are not being suppressed

A webhook consumer that logs bounces but does not add them to the suppression list, or a feature flag that quietly turned the suppression off during a migration.

Hard bounces suppressed automatically

Spam report received at Gmail

Complaint rates are climbing

A broadcast to an old list, a transactional message that reads like marketing, or an unsubscribe link that was broken in the last template refactor. Gmail reads complaints very seriously.

Complaints investigated and lowered

Webhook signature invalid: timestamp

Webhooks are being rejected after a delay

A consumer that queued webhooks for later processing and is now reverifying signatures outside the five-minute window. The fix is to verify once on ingest and trust the queued record afterwards.

Webhooks verified once, processed later

What we do

Resend help, API to inbox

Call in for one undelivered message, or let us run the whole sending domain.

Rescue
Sends failing, bounces piling up, or a sudden spike in Gmail spam placement. We stabilise sending first and write up the real cause second.
Deliverability and DNS
SPF, DKIM, DMARC, BIMI and MTA-STS reviewed against the domain's other senders, alignment fixed, aggregate reports read and acted on.
React Email templates
Components tested against the real mailbox providers, dark-mode handled, unsubscribe and legal footers correct, and the preview environment matched to what Outlook actually renders.
Webhook handling
Signed webhook verification, idempotent consumers, bounce and complaint suppression wired to the product, and retry behavior that matches Resend's semantics.
Migrations
Moving from SendGrid, Postmark, Mailgun or SES onto Resend without a dip in deliverability during the transition.
Managed Tech
Weekly deliverability reviews, DMARC aggregate reports read and summarized, suppression list growth tracked, and an engineer on call when a mailbox provider changes the rules again.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Resend alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Resend questions

Something else? Call+1 737 727 7327

Why do my Resend emails land in Gmail spam?

Three usual causes: DMARC alignment failing between the From domain and the DKIM-signing domain, a complaint rate that has already pushed the domain into Gmail's suspect bucket, or content that trips on common spam heuristics (urgent subject lines, lots of images, few words). We work through aggregate DMARC reports, the message-level logs and the templates, and bring placement back without a single silver bullet.

How do I verify my Resend domain correctly?

Resend gives you a set of DNS records for SPF, DKIM and a Return-Path. The common mistakes are adding the SPF include when the domain already includes two other providers and exceeds ten lookups, wrapping the DKIM TXT value in extra quotes, or forgetting to set the DMARC record to anything useful. We check the DNS end-to-end and verify alignment with a test send, not just a green tick in the dashboard.

Why do my React Email templates look wrong in Outlook?

Outlook on Windows uses the Word rendering engine for HTML emails, which handles CSS very differently from Gmail or Apple Mail. Flexbox, modern CSS properties and some inline styles simply do not work there. The fix is to render the template in the actual client (not just the preview), swap flex layouts for table-based ones in the affected components, and keep a test matrix of the mailbox clients you care about.

How should we handle bounces and complaints?

Every bounce webhook should add hard bounces to the suppression list automatically, and complaints should both suppress the recipient and alert the team. Soft bounces (temporary delivery failures) are usually safe to retry up to a limit and then suppress. The exact policy depends on your volume, but the goal is to avoid ever sending to an address that has already hard-bounced or complained.

Can we migrate from SendGrid or SES to Resend?

Yes, and the real work is the templates, the DNS alignment and the suppression list, not the SDK swap. We bring across the suppressions, re-verify the domain with Resend's records alongside the existing ones for a warm-up period, port the templates to React Email or keep them as HTML, and move traffic in stages rather than in one cutover.

How much does Resend help cost?

A free quote is the first step. Describe what domain you send from and what is misbehaving, and we return a scope and a fixed fee before we edit a DNS record or touch a template.

Free estimate

Resend giving you trouble?

Domain setup, deliverability, React Email templates, webhook handling and migrations from older senders. We pick up any of them.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.