That gap between 1 and 7 is where open rates collapse, sender scores bleed out, and campaigns die without ever knowing why. The Signal Engine reads all 7. Here's what each one measures, why it matters, and what your list is broadcasting right now that nobody else is reading.
Get my Signal Score in 30 seconds →Not authentication. They had that. Not list cleaning. They did that. Not a better subject line or a warmer sending domain or a more engaged segment.
They were missing 5 of the 7 inbox signals their list was broadcasting.
And nobody told them those signals existed. Not their ESP. Not ZeroBounce. Not Mail-Tester. Not GlockApps. Because none of those tools were built to read them.
Here is what was invisible to you. And what InbXr was built to reveal.
Every tool shows you a backward number: how many emails bounced in the last send. By the time that number appears in your dashboard, the damage is already in your sender score.
Claim: Your bounce rate is a lagging indicator. It tells you about damage already done.
Proof: Domains age and expire. MX records change. Catch-all addresses accept every email and bounce later. Valid-today addresses become invalid-tomorrow at a rate that is calculable before you send.
Benefit: Bounce Exposure reads 30 to 60 days forward, flags which contacts carry elevated bounce risk right now, and tells you before you send. Not after you have paid for it with your sender reputation.
In September 2021, Apple launched Mail Privacy Protection. It prefetches emails automatically before anyone opens them. And registers that prefetch as an open. Your ESP counted it. Your deliverability tools scored it. Your campaign reports showed it.
None of it was real.
Claim: Every open rate in the market has been inflated since Apple Mail Privacy Protection launched.
Proof: Apple devices automatically trigger open-tracking pixels for every email they receive, regardless of whether a human ever saw the email. Open rates across all ESPs are inflated by an estimated 20 to 40% as a result. No tool on the market removes this distortion from their engagement scoring except InbXr.
Benefit: Engagement Trajectory removes the machine opens and measures where your real human engagement is heading. Weighted by clicks and replies, not prefetched pixel fires. Most InbXr users discover their real engagement rate is significantly lower than their ESP dashboard shows. That gap between what they thought and what was real is where deliverability decisions go wrong.
A list of people who opted in organically and a list of cold-outreached or purchased contacts look identical to a verifier. Same syntax checks. Same MX lookups. Same SMTP responses. Pass, pass, pass.
They perform completely differently from day one.
Claim: Where contacts came from predicts how they will behave. And most tools have no way to tell the difference.
Proof: Segments where fewer than 15% of contacts engaged in the first 30 days after joining carry a cold acquisition signal. That signal predicts bounce rate, spam complaint rate, and sender reputation degradation at measurably higher levels than organic opt-in cohorts. Before a single campaign is sent to them.
Benefit: InbXr infers acquisition quality from contact behaviour. Without you declaring anything. It identifies which segments of your list came from cold or poor-quality acquisition and flags them before you send a campaign their way. No other tool in the market reads this.
Every tool checks whether your sending domain is blacklisted. That is one side of the equation and every tool covers it.
Claim: One-sided reputation checking misses half the picture.
Proof: ISPs filter based on the sending domain AND the receiving domain concentration inside your list. A sender with a clean domain sending to a list where 40% of contacts are on Yahoo and AOL. After their 2025 filtering changes. Carries elevated deliverability risk regardless of their own sender reputation.
Benefit: InbXr reads both sides simultaneously. Your domain reputation and the receiving domain composition of your list. Yours and theirs.
Spam traps do not announce themselves. They sit inside old, dormant, poorly-acquired lists and wait.
Claim: Spam trap risk is calculable before you send. Based on the conditions that produce trap hits.
Proof: Lists with high proportions of very old inactive contacts from unknown or cold acquisition sources hit spam traps at measurably higher rates than recently engaged organic lists. The conditions. List age, dormancy depth, acquisition source pattern. Are all readable before the send.
Benefit: InbXr calculates that probability and scores it against your list before the campaign goes out. It flags the specific segment most likely to carry trap risk so you can suppress them first, not discover them after.
Gmail and Yahoo mandated SPF, DKIM, and DMARC for bulk senders in 2024. Microsoft followed in May 2025 with stricter requirements.
Claim: Thousands of senders have a DMARC policy of p=none right now and do not know it is causing them to fail Microsoft's 2025 bulk sender requirements.
Proof: Microsoft's May 2025 mandate requires a DMARC policy of p=quarantine or p=reject for bulk senders. p=none. Which passes the basic presence check and shows as "DMARC: present" in most tools. Fails this requirement.
Benefit: Authentication Standing scores your full posture against each ISP's current requirements. Not just whether records exist. It flags every gap against the specific 2025 mandate it fails and generates the exact DNS records that fix it. Copy. Paste. Done.
Your at-risk contact segment is either growing or it is not. If it is growing, it is growing at a rate. That rate projects to a date when the damage becomes unavoidable.
Claim: List health is not a static score. It is a direction and a velocity.
Proof: The weekly rate at which contacts migrate from active to warm to at-risk to dormant is calculable from ESP sync data. That rate, projected forward, produces a date: the point at which the Signal Score crosses the danger threshold and deliverability damage becomes statistically likely.
Benefit: InbXr tells you how many days you have before your signal score hits the danger threshold. "Your at-risk segment is growing at 340 contacts per week. At this rate you will cross the danger threshold in 18 days." That sentence does not exist in any other deliverability tool in the market. That is the difference between a rearview mirror and a windshield.
Five signals, unread, while your deliverability degraded and your revenue leaked out on every send. The signals were not new. They were broadcasting the whole time. The tools you trusted were simply not built to hear them.
InbXr reads all 7 simultaneously. Every 6 hours. Across every connected ESP. In plain English. With the fix built in.
Evaluate through The 7 Inbox Signals. Execute through The 7 Inbox Signals. Get your email to the inbox and your copy to sell.
You now know what 5 of them are. The question is which ones are firing in your list. And how loud.
Reveal what's burning my revenue → Free · No credit card · First reading in 60 seconds"My open rates dropped 40% and nothing changed."
Your open rate was already wrong before it dropped. Apple MPP inflated it for years. Machine prefetches counted as human opens. When real engagement fell, the gap between the number and reality finally became impossible to ignore. Engagement Trajectory would have flagged the real decline long before it showed up in your report.
"I verified my list, authenticated my domain, and still got flagged."
Verification reads Signal 01. Authentication is Signal 06. You were clean on both. And still had 5 signals broadcasting problems your stack was not built to hear. Acquisition Quality and Spam Trap Exposure were the ones that got you.
"I inherited a 200k list with no history attached."
Upload it as a CSV. Get a full 7 Signal reading in 60 seconds. No ESP connection required. Most inherited lists fail 3 signals before the first send goes out. Now you will know which 3 before you touch them.
"I got flagged, lost my sender score, and it took months to recover."
Pre-send Check and Early Warning read the exact conditions that produce that event. Before you send, not after. Once is expensive. Twice is avoidable.