Frequently asked

Common questions.

How arc-relay works, who it's for, and why forwarded email breaks without it.

01Who is arc-relay for?

Five honest fits.

I use a custom domain but receive mail in Gmail / Outlook

The problem: You own yourname.com for professional credibility, but your actual inbox is a free provider like Gmail. Standard forwarding breaks DMARC alignment, so newsletters, invoices, and client emails get flagged as spam or silently dropped.

How arc-relay helps: Point your domain's MX records to arc-relay. We ARC-seal forwarded messages, recording the SPF, DKIM and DMARC results checked when they arrived (if the newest ARC seal on an arriving message already reports a failed chain, ARC-Relay forwards it without adding its own). Receivers that trust ARC seals can use those recorded results when the forward itself fails SPF or DMARC. Whether they do, and where they file the message, is their decision.

Perfect for freelancers, solo founders, and anyone who wants a professional email without managing a full mailbox.
I run multiple brands or domains under one company

The problem: Your company operates 10+ brands, each with its own domain. Maintaining separate mailboxes per domain is expensive, fragmented, and hard to manage. Forwarding everything to a central inbox causes DMARC failures across the board.

How arc-relay helps: Point all your domain MX records to arc-relay. Every brand's inbound mail is forwarded to your central inbox, ARC-sealed and SRS-rewritten. The dashboard gives you one-pane visibility across all domains.

One inbox. Ten brands. One dashboard.
I'm an agency managing email for clients

The problem: You set up email forwarding for clients, but their newsletters and transactional emails break DKIM/DMARC alignment downstream. The client blames your infrastructure when messages land in spam.

How arc-relay helps: SRS envelope rewriting plus ARC sealing means you can forward client mail without breaking sender reputation. Per-domain logs in the dashboard show what was received, rejected, and handed on for delivery.

Manage client email forwarding professionally. Show them the analytics to prove it works.
I route email through a security gateway or filter

The problem: Your organization routes inbound mail through spam filters, DLP, or archival systems. These gateways modify message headers during processing, breaking the original DKIM signatures.

How arc-relay helps: The ARC chain vouches for the original authentication results before the message was modified in transit. Receiving servers that trust ARC seals can use those results instead of the failures the forwarding hop caused; whether they do is their decision.

Add security layers in front of your mailboxes without destroying sender authentication.
I own many domains and want to catch email on all of them

The problem: You own dozens of domains — legacy brands, typo-squats, future projects. You want to receive email sent to any of them, but provisioning separate mailboxes is wasteful and expensive.

How arc-relay helps: Add each domain in 30 seconds — just point the MX records, no mailbox provisioning needed. Forward everything to a single address. Solo covers 1 domain free; Pro gives 50; Studio is unlimited.

Park the domain. Keep the email. Free forever on Solo.
02How does it work?

The plumbing.

What is ARC and why does it matter?

ARC (Authenticated Received Chain) is an email authentication protocol, published in 2019 as an Experimental RFC (RFC 8617), that records authentication results across intermediary hops. When an email is forwarded, the original DKIM signature often breaks because headers get modified in transit.

Each intermediary server can seal the authentication results it observed. A receiver that checks ARC and trusts the sealer can use those recorded results even when the original DKIM signature no longer validates. Whether it does is its decision, and most receivers don't publish how much weight they give a seal. ARC's standing at the IETF is changing: see Is ARC being retired? below.

What is SRS and how does it fix SPF?

SRS (Sender Rewriting Scheme) rewrites the envelope sender address so the forwarded message comes from arc-relay's domain rather than the original sender's domain. This means the receiving server checks SPF against arc-relay.com, which passes because arc-relay is the actual sending server.

Without SRS, the receiving server would check SPF against the original sender's domain, which would fail because arc-relay's IP isn't authorized for that domain. SRS is invisible to the end user — the displayed "From" address stays the same.

What about DKIM? Do you re-sign forwarded messages?

All plans preserve the original DKIM signature. Our ARC seal records, under our signature, whether DKIM verified when the message reached us, and receivers that trust ARC can take that into account.

Pro and Studio plans can optionally enable per-domain DKIM signing. This generates an RSA 2048-bit key for your domain and adds a DKIM-Signature header to every forwarded message. You add one DNS record and it activates automatically.

Per-domain DKIM is optional. It adds a signature from your own domain to forwarded mail, which a receiver can check whether or not it uses ARC.

How do I set up my domain?

Three steps:

  1. Add your domain in the dashboard
  2. Set your MX record to 10 mx.arc-relay.com
  3. Add the TXT verification record we provide

DNS changes usually propagate in under 5 minutes. Once verified, email to your domain is forwarded automatically, with SRS rewriting and an ARC seal.

Which email providers check ARC?

It's up to each receiver, and few publish how they use ARC. Microsoft 365 documents it: admins can list the ARC sealers their organization trusts. Google's current guidance for forwarding to Gmail asks forwarders to rewrite the envelope sender, which is what SRS does, and doesn't mention ARC.

ARC-Relay rewrites the envelope sender with SRS and adds an ARC seal. What a receiver does with them is its decision.

Is ARC being retired?

Possibly, on paper. As of October 2026, the IETF's DMARC working group has a draft (draft-ietf-dmarc-arc-to-historic) that would reclassify ARC (RFC 8617) as Historic, with a target of November 2026. It has not been approved yet.

Historic means the IETF no longer recommends ARC. It doesn't switch anything off: receivers that check ARC seals today can keep doing so, and SRS, the other half of what ARC-Relay does to forwarded mail, is not affected. The IETF's in-progress successor for forwarded mail is DKIM2 (draft-ietf-dkim-dkim2-spec), still a draft.

We update this answer as the drafts move. Last checked 17 October 2026.

03Pricing & plans

What it costs.

Is there a free plan?

Yes. The free Solo plan covers 1 domain and up to 5 aliases, forever — no credit card required. See all plans.

What happens if I hit my forward limit?

Incoming mail will be temporarily rejected with a retry code, so the sending server holds it in queue. No email is lost — the sender's server will retry. Upgrade your plan or wait for the monthly reset and forwarding resumes automatically.

Still have questions?

Reach us at [email protected] — we typically reply within a few hours.

Ready to fix your forwarding?

Set up in under 2 minutes. Solo, Pro, and Studio plans.

Get started free →