SFMC Deliverability Incident Analyzer

The hour you spend guessing is the hour the sender score drops

The bounce data arrives as a wall of SMTP codes and the triage starts as a list of suspects: reputation, authentication, an ISP block, bad data, a volume spike. Each one takes a different person and a different fix, and picking wrong costs you the window.

Meanwhile the damage compounds. Reputation is scored on a rolling basis, so every further send into a block makes the recovery longer. Speed of diagnosis is not a nice-to-have here — it is most of the outcome.

Bounce codes already contain the diagnosis

A block bounce from one provider and a hard bounce across all of them are different incidents with different causes. Microsoft refusing you while Gmail keeps accepting is a reputation or authentication story at one receiver. Hard bounces spread evenly across providers is a data story. Technical bounces clustered in a window is usually something you changed.

The pattern is already in the export. The analyzer reads it rather than making you eyeball it.

What it returns

Your bounce rate and the exact window the incident happened in. A provider breakdown, so you can see immediately whether one receiver is doing the blocking or all of them are. The bounce mix split into block, hard, soft and technical. The single most likely cause, with the rows that support it. And a check-first list in priority order, so the next hour goes on the right thing.

It runs entirely in your browser — the export never leaves the machine, which matters when the file is full of customer addresses.

Why it is a file and not a website

A bounce export is a list of your customers’ email addresses. Pasting that into a web page is a conversation most security teams end quickly, and they are right to — “trust us, the page does not upload anything” is not something anyone can verify from the outside.

So the analyzer ships as a single self-contained HTML file. It makes no network calls of any kind: no upload, no analytics, no external scripts, no web fonts, no remote images. Even the logo is embedded in the file. Disconnect from the internet and it still works, which is the test worth running.

Open it in any text editor and search for fetch, XMLHttpRequest, sendBeacon or script src. There are none. Your security team can clear it in about two minutes, and the _Bounce query and a sample export are in the archive alongside it.