What is the 60 40 rule in email?

There is no standard email rule by that name. No mailbox provider, RFC, or deliverability body defines a 60 40 rule, so anyone quoting it should tell you what the two numbers measure and where the figure came from. Until they do, do not use it as a benchmark for your own sending.

Is 35% a good email open rate?

It can be, but the number on its own tells you very little. Open rates depend on how your platform counts an open, what kind of mail you sent, and which mailbox providers your list uses, so 35% only means something next to your own comparable send. An open rate also says nothing about whether mail was delivered or where it landed.

What is the 30 30 50 rule for cold emails?

There is no recognized cold email rule by that name. The people who use the phrase do not publish a methodology behind it, so treat it as a marketing label rather than a benchmark. Ask what each number measures, and over what period, before you act on it.

What is the 12 second rule for emails?

There is no recognized 12 second rule in email deliverability. No mailbox provider or standards body defines one, and no timing rule can tell you whether your mail was delivered or where it landed. Use your own delivery and placement data, split by provider, instead.

Can a good delivery rate prove inbox placement?

No, because delivery and placement answer different questions. A delivery result tells you the receiving server accepted the message. It does not tell you whether that message reached the inbox, the spam folder, or somewhere else the receiver decided to put it.

Should I compare all mailbox providers together?

No, compare each mailbox provider separately wherever your sending platform gives you that view. An account-wide average can stay flat while results at one provider drop sharply, and that drop is exactly what you need to see. Compare each segment against a comparable earlier period.

What is a good email deliverability rate?

A good email deliverability rate is not one universal percentage. Judge performance by separating technical delivery from inbox placement, then comparing results by mailbox provider, message type, and time period. A rate that looks acceptable in an aggregate dashboard can still hide weak placement or a material change at one provider. The most useful benchmark is your own stable, segmented baseline and any change that needs investigation.

At a glance

Quick takeaways

Delivery tracking and inbox placement are separate signals.
No permitted primary source establishes one good or average email deliverability percentage.
Compare results by mailbox provider instead of relying only on an account-wide total.
Compare similar message types and periods before treating a change as meaningful.
Domain authentication is a relevant sender-side diagnostic area, but it does not guarantee inbox placement.
A public DNS or security check cannot reveal a receiver's private placement decision.

How email deliverability performance works

Email performance has more than one layer. A sending platform can track whether mail was delivered, while inbox placement asks where a receiving mailbox provider placed accepted mail. Litmus describes inbox placement, domain reputation, and engagement patterns as separate deliverability signals. Mailjet likewise presents delivery tracking and inbox landing as distinct parts of its email deliverability product page.

That distinction matters when someone asks for a good rate. An aggregate delivery result can answer one operational question: whether a platform reports messages as delivered. It cannot, by itself, show whether recipients saw those messages in the inbox, whether one mailbox provider produced different results, or whether a recent change affected a particular type of campaign.

For the underlying terminology, see email deliverability. This page answers how to interpret a result, rather than supplying a percentage that would imply comparable measurement across every sender and provider.

Mailbox-provider segmentation is also useful. Mailtrap describes showing key deliverability metrics for every mailbox provider. That product statement supports a practical operating rule: if provider-level views are available, inspect them before deciding an aggregate rate is good or bad.

Flow showing how to assess an observed email delivery result by separating delivery, inbox placement, provider segments, and sender-side checks — Source: Palisade.

When a good rate changes

The answer changes when the comparison changes. A delivery result from marketing mail may not be comparable to transactional mail. A result across all mailbox providers may not describe what happens at one provider. A current result may also be less useful than its direction against a stable baseline.

Use this decision rule:

Treat delivery and inbox placement as separate measures when both are available.
Compare the same kind of mail with an earlier, comparable period.
Segment by mailbox provider where the sending platform provides that view.
Investigate a material change in one segment before accepting an account-wide average as healthy.
Review sender-side evidence, including domain authentication, when the change points to a sending-domain issue.

Mailjet groups deliverability monitoring, reputation protection, dedicated IP addresses, and domain authentication in its deliverability offering. That does not establish that any one control produces a particular rate. It does mean authentication is a reasonable diagnostic branch when investigating sender-side conditions.

A receiver still makes its own delivery and placement decisions. Stronger authentication can support trustworthy mail handling, but it cannot guarantee delivery or inbox placement. Broader context is available in the email deliverability hub.

A worked deliverability-rate assessment

Suppose an email team sees a lower reported delivery result this week. The useful question is not "is this percentage above a universal benchmark?" Start by making the observation comparable.

Technical exampletext

Assessment period: Current week versus the previous comparable week
Message type: Product announcements only
Segments: Each available mailbox provider
Signals to compare:
- Reported delivery result
- Available inbox-placement result
- Domain reputation and engagement views, if available
- Published sender-authentication DNS evidence
Decision: Investigate any material segment-level change before judging the aggregate result

This is a decision format, not a formula. It avoids treating all sends as identical and keeps each evidence type in its proper scope.

For example, an unchanged account-wide figure does not settle the question if one mailbox-provider segment declines while another rises. Similarly, a strong inbox-placement result for one type of message does not prove the same result for a different sending path.

If the evidence points toward authentication, inspect the published DNS record separately from the delivered message path. A DMARC record lookup can show public DMARC DNS evidence. It cannot prove that a particular production message authenticated, that every legitimate sender aligns, or that a mailbox provider will place future messages in the inbox.

What to check next

Choose the next action based on the evidence you have:

If you only have an aggregate delivery result, find a comparable prior period and split the available results by mailbox provider and message type.
If you have inbox-placement information, compare it with delivery instead of treating either measure as a substitute for the other.
If one provider or sending domain changes materially, review the sender-side signals available in your sending platform, including reputation and authentication-related evidence.
If you need a foundation before interpreting the data, read email deliverability questions, answered.
If delivery failures are the issue rather than placement, compare the result with what is a good email bounce rate?.

A delivered message is still the strongest evidence for the exact path it took. Where possible, review the sending platform's provider-specific data and the message evidence for that same production path. Public DNS results and security checks are narrower signals.

Inspect the sender-side security posture behind the result

When a rate changes and you need a starting point for sender-side investigation, inspect the sending domain's public email-security posture before assuming that one aggregate percentage explains the issue.

Inspect the email security score

A public domain check cannot measure inbox placement, prove a receiver's private reputation decision, monitor the production sending path, or guarantee future delivery. For ongoing DMARC work, Palisade's AI-first, agent-first DMARC software analyzes aggregate-report data, identifies authentication and alignment issues, and proposes next policy steps for human review.

Start with Palisade

Evidence