ARC (Authenticated Received Chain)
A protocol that preserves original authentication results across intermediaries like mailing lists and forwarders.
Glossary
Plain-language definitions for email deliverability and infrastructure terms: authentication, reputation, compliance, and the API concepts behind them.
Read the deliverability blog or the API docs for how these terms apply in practice.
A protocol that preserves original authentication results across intermediaries like mailing lists and forwarders.
A standard that displays a verified brand logo next to authenticated emails in supporting inboxes.
A cryptographic signature added to outgoing mail that lets receivers verify the message wasn't altered in transit.
A DNS policy that tells receivers what to do with mail claiming to be from a domain that fails SPF and DKIM alignment.
The requirement that the domain in SPF or DKIM matches (exactly or by organizational domain) the visible From address.
A policy mechanism that requires SMTP delivery to a domain to use TLS with a valid certificate, preventing downgrade attacks.
The address bounce notifications are sent to, which SPF actually authenticates instead of the visible From address.
A DNS TXT record listing which mail servers are allowed to send email for a domain.
A published list of IP addresses or domains flagged as sources of spam, checked by receiving mail servers in real time.
Sorting a non-delivery response into a category (hard, soft, block, etc.) that determines whether and how to retry.
The percentage of delivered messages a recipient marks as spam, one of the most heavily weighted deliverability signals.
Mailbox providers using recipient behavior (opens, clicks, deletes without reading) as a primary signal for inbox versus spam placement.
A subscription with a mailbox provider that forwards spam-complaint notifications back to the sender in near real time.
A permanent delivery failure, typically because the recipient address doesn't exist, that should never be retried.
The share of delivered messages that land in the primary inbox rather than a spam or promotions folder.
A gradual, engagement-weighted volume ramp used to establish reputation for a new sending IP or domain.
Ongoing practices that keep a mailing list free of invalid, unengaged, or risky addresses before they damage reputation.
Sending to a panel of monitored test addresses across mailbox providers to check where a message actually lands before or after a real send.
A mailbox provider's ongoing assessment of a sending IP and domain, built from bounce, complaint, and engagement history.
A temporary delivery failure, such as a full mailbox or a transient server issue, that is safe to retry.
An email address that was never legitimately opted in, used by mailbox providers and blocklists to identify poor list-acquisition practices.
A sending IP address used exclusively by one sender, whose reputation reflects only that sender's own sending history.
Routing transactional and marketing (or per-tenant) traffic through separate sending identities and IP pools so one traffic class can't damage another's reputation.
The software that routes and delivers email between mail servers over SMTP.
A DNS record that specifies which mail servers accept email for a domain, and in what priority order.
A DNS record that maps a sending IP address back to a hostname, checked by many receivers as a basic legitimacy signal.
A set of sending IP addresses used by multiple senders, whose collective reputation each tenant relies on.
The internet-standard protocol used to transmit email between mail servers.
Deliberately capping the rate of outbound connections or messages to a receiving domain to stay within its tolerance and avoid triggering blocks.
The US federal law setting baseline requirements for commercial email: accurate headers, a working unsubscribe, and a physical postal address.
A retained, timestamped record of how and when a recipient agreed to receive marketing email, kept for compliance review.
Requiring a recipient to confirm their email address via a follow-up link before they're added to a sending list.
The EU/UK GDPR requirement that marketing email generally needs a freely given, specific, informed, opt-in legal basis before sending.
An email header that lets recipients unsubscribe with one click from within their mail client, without opening the message.
A record of addresses that must never receive mail again, populated from unsubscribes, hard bounces, and complaints.
Email sent to many recipients at once for promotional or informational purposes, not triggered by an individual user action.
A discrete, timestamped record of something that happened to a specific email after it was sent: accepted, delivered, bounced, opened, and so on.
A client-supplied identifier that lets an API safely retry a request after a timeout without risking a duplicate send.
Free dashboards mailbox providers (notably Google and Microsoft) offer senders to monitor domain reputation and delivery signals directly.
The domain used in the From address of outgoing mail, which is where authentication and reputation are anchored.
Email triggered by a specific user action or system event, such as a password reset, receipt, or shipping notification.
An HTTP callback the sending platform makes to a customer's endpoint to report a delivery event as it happens.