Article
How to Write an Appeal to Your ESP After Suspension: A Step-by-Step Guide
By Unlimited Verifier Team ·

Summary
To appeal an ESP suspension caused by bounces, send a short letter that names the root cause, states exact suppressed and verified counts, and commits to a capped re-entry plan under 2% bounces. Reviewers judge whether the risk to shared infrastructure is controlled, so attach evidence that backs every number in the letter.To appeal an ESP suspension after bounces, send the compliance team a short written letter that states the root cause, the exact counts of addresses you suppressed and verified, and a capped re-entry plan that keeps bounces under 2%. A common reason appeals fail is that the sender says the list is clean without being able to show it, so the evidence behind the letter matters as much as the wording. For the broader picture of why suspensions happen, start with our high bounce rate account suspension guide.
Quick answer
- Name the mechanism in your root-cause sentence. "We imported 18,000 contacts from a file that had never been mailed" works. "We had some bad data" does not.
- Gather four evidence items before you write: the bounce breakdown, your suppression log, a verification summary, and a dated re-entry calendar.
- Put the bounce rate, its denominator and the raw counts in your first paragraph so a reviewer can check them in seconds.
- Commit to a tripwire. Promise to pause and notify the ESP if any send exceeds 1% bounces.
- Keep the letter to roughly 250–300 words and attach the evidence rather than pasting it in.
What is an ESP appeal supposed to accomplish?
An ESP appeal has one job: convince a reviewer that the risk you pose to shared infrastructure is under control. The reviewer is not judging whether you are a good sender. They are asking two questions: did you understand what caused the bounces, and what stops it from happening on the next send?
Restrictions are often triggered automatically and then reviewed by people. Your letter is effectively a short risk memo, so write it as one. Every sentence should reduce the reviewer's uncertainty about the cause, quantify the damage, or describe a control that is still in place.
Bottom line: Write the appeal as a risk memo for someone protecting shared IP addresses, not as an apology.
Who reads your appeal, and what are they checking?
Appeals are commonly handled in two stages, though each platform differs. A first-line reviewer checks whether the basics are present: a stated cause, a cleaning action and some kind of plan. Anything that looks like a manual case is escalated to a compliance or deliverability team, who read more carefully and ask follow-up questions.
Reviewers skim fast, so they look for specific signals:
| What the reviewer checks | Why it matters | Red flag in your letter |
|---|---|---|
| Does the cause match the metric in the notice? | Answering a different problem suggests you haven't read the notice | Discussing complaints when the notice cited bounces |
| Are the numbers internally consistent? | Mismatched counts suggest the cleaning was not really done | A bounce rate that doesn't match the bounces and sends you list |
| Is there evidence beyond a sentence? | Claims without data are common and rarely enough | "We have cleaned the list" with no counts |
| Is the re-entry plan restrained? | Ambition right after a spike looks like the behaviour that caused it | Sending the full list on day one |
| Is there a measurable commitment? | Reviewers need a way to hold you to your promise | "We will monitor bounces closely" with no threshold |
One detail trips up many senders: the denominator. Define bounce rate as bounces divided by messages attempted for the same campaign, and say so. Mixing up list size and send volume is a common reason reviewers can't reconcile a letter with the notice.
ESP review processes aren't public, so treat these checks as a common pattern rather than a guarantee of how any one provider will review your case. For platform-specific context, see our guides on Mailchimp suspension steps, the SendGrid under-review status, the Brevo suspension guide and Mailgun bounce warnings.
Bottom line: Reviewers check consistency, scope, proof and restraint. Build your letter around those four things.
What evidence should you gather before you write?
Gather evidence first and draft second. If you write the letter before you have the numbers, you will end up writing around the gaps. This is the evidence set that does the most work:
| Evidence | What it proves | How to produce it | How to attach it |
|---|---|---|---|
| Bounce breakdown for the flagged send | The scope of the problem | Campaign report with hard bounces, soft bounces, complaints and unsubscribes listed separately | Short table in the letter |
| Suppression log | Bounced addresses were actually removed | ESP export, plus your own copy with reason codes | Counts in the letter, CSV on request |
| Verification summary | The rest of the list was checked, not assumed | Valid, Risky and Invalid counts from your verifier | Exported summary attached |
| Source or consent record | Contacts came from a known, opted-in source | Import file names, form names, double opt-in timestamps | Two-line summary, raw data on request |
| Re-entry calendar | You will ramp slowly and within limits | Dated table of audience, volume and bounce ceiling | Table in the letter |
| Process change list | The cause won't recur | Written rules, such as "no import goes out before verification" | Bulleted list in the letter |
Two details are easy to miss. First, suppressed is not the same as deleted. Reviewers want both: the address removed from your sending lists and recorded on a suppression list. Second, keep your own copy of the suppression data. Suppressions don't always travel with your contacts when you export or migrate, and you may need them later.
Save your verification summary immediately, too. Retention differs by plan: Unlimited Verifier's Free plan keeps results for 24 hours, while Pro keeps them for 30 days. Export the summary the day the job finishes, store it somewhere you control, and label it with the date.
For the first 48 hours after a spike, our five-step spike response covers the immediate actions.
Bottom line: Gather the suppression log, verification summary and source records before you draft. Export the verification results within their retention window.
How should you structure the appeal, section by section?
A strong appeal follows the same order every time, because reviewers scan for the same things in the same places. Each section answers a question the reviewer would otherwise have to ask you.
Subject line: identify the account, metric and date
Include the account ID, the metric named in the notice, the campaign and the date. A reviewer triaging a queue should be able to match your message to the case without opening it. A vague subject like "Please review my account" slows everything down.
Opening: state the facts in two sentences
Say what happened and what the rate was, with the denominator. For example: "On 3 March, our campaign to 72,400 contacts recorded 1,880 bounces, a 2.6% bounce rate calculated as bounces divided by messages sent." The reviewer now knows you understand the problem and can check your arithmetic.
Cause: one sentence that names the mechanism
Describe what, when, how many and where it came from. This is the sentence that earns or loses credibility, and it's covered in detail in the next section.
Actions taken: the counts
List what you suppressed and what you verified, with numbers. Show the split between Valid, Risky and Invalid. This section turns "we cleaned the list" into something a reviewer can check.
Re-entry plan: volume, audience and a tripwire
Describe who you will mail first, how volume will rise, and the bounce ceiling for each send. Add the tripwire: "If any send exceeds 1% bounces, we will pause and notify you before the next send." That promise makes the plan credible, because it shows you have planned for failure.
Prevention: the process change
Name one or two controls that operate where bad data enters, such as real-time validation at signup or verifying every import before upload. Specific controls beat general intentions like "we are committed to list quality."
Close: offer the evidence
End by offering the suppression log, the verification export or per-send metrics. This signals that your numbers can be checked, and that you expect the reviewer to check them.
Bottom line: Subject, facts, cause, counts, plan, control, offer. Keep that order and the reviewer can find everything on the first read.
How do you write the root-cause sentence?
The root-cause sentence is where most appeals lose credibility. Reviewers have read "a data issue" and "a third-party file" many times, and they tend to read those phrases as evasion. The fix is to name a mechanism: a specific source, a specific date, a specific count and the specific reason the data wasn't checked.
Here are three versions of the same cause, in ascending order of usefulness:
- Weak: "We had some bad emails in our list."
- Better: "Our list had a lot of old contacts."
- Strong: "On 3 March we imported 18,000 contacts from a 2022 trade-show file that had never been mailed, and sent them in the same campaign as our main list without verifying them first."
The strong version does three things. It tells the reviewer where the bad addresses came from, it shows the failure was a process gap rather than a random event, and it gives the reviewer a control to check: imports now go through verification before upload.
B2B and SaaS senders are especially exposed here. Trade-show leads, old CRM exports and partner lists all age quickly, and the email verification for ecommerce and SaaS approach of verifying before every send is the control that closes this gap.
If you bought or scraped the list, say so. It feels risky, but reviewers distinguish between a mistake and a practice. A candid admission followed by a firm change of practice is more credible than a vague explanation that later turns out to be incomplete. If the spike followed a migration, see our guide to bounces after changing ESP, because those spikes often come from suppression data that didn't carry over.
A practical test: if your root-cause sentence could describe almost any sender, it is too vague. A reviewer should be able to picture your situation from it alone.
Bottom line: Name the source, the date, the count and the missing control in one sentence. Specificity reads as honesty.
Which phrases weaken an appeal, and which strengthen it?
Small wording choices change how a reviewer reads the whole letter. The table below pairs phrases that read as warning signs with stronger alternatives. The stronger versions aren't more polished; they are more checkable.
| Weak phrase | Why it hurts | Stronger version |
|---|---|---|
| "We have cleaned our list." | No proof, and no way to check | "We suppressed 1,880 bounced addresses and verified the remaining 70,479; 61,200 are Valid." |
| "This was a one-off." | Unverified, and reviewers have heard it before | "This came from [mechanism]. We have added [control] to prevent recurrence." |
| "Our vendor's data was bad." | Shifts ownership away from you | "We imported a file without verifying it. We now verify every import before upload." |
| "Our list is 100% opt-in." | An unprovable absolute | "Every contact in the affected segment has a double opt-in timestamp; a sample is available." |
| "Our bounce rate was about 2%." | Vague, and no denominator | "1,880 bounces from 72,400 messages sent = 2.6%." |
| "We need to get back to normal sending quickly." | Signals pressure to resume | "Day 1 is capped at 4,000 contacts; we will adjust if you advise a different ramp." |
The pattern is the same across all six. The weak phrase asks the reviewer to trust you. The strong phrase gives them something to verify or a commitment to hold you to.
Bottom line: Replace every claim you can't prove with a number, a source or a control.
What does a complete appeal look like?
The template below is built for a manual review, the tier where a full letter matters most. Replace the bracketed fields with your figures and keep the total near 250–300 words.
Subject: Remediation plan, account [ID], bounce rate on [campaign name], [date]
Hello [name or compliance team],
On [date], our campaign "[name]" to [N] contacts recorded [N] bounces, a [X]% bounce rate calculated as bounces divided by messages sent. The cause was [one sentence: what, when, how many, where it came from].
We have paused all sending. We suppressed [N] hard bounces, [N] soft bounces that failed across repeated sends, and [N] complaints or unsubscribes. We then verified the remaining [N] addresses for syntax, domain, MX records and mailbox status. Of these, [N] are Valid, [N] are Risky (including catch-all and role-based addresses) and [N] are Invalid, which we have removed. Summary counts are attached.
Our re-entry plan sends only to Valid contacts who engaged in the last [30/90] days. Volume rises from [N] on [date] to [N] on [date], with a bounce ceiling of 1% per send. If any send exceeds that ceiling, we will pause and notify you before the next send.
Going forward we will [verify at signup / verify every import before upload / re-verify quarterly], and [one additional control].
We are happy to share the suppression log, the verification export and per-send metrics during the ramp. Please let us know what you need.
[Name, role, account ID]
Each paragraph has one job. The first delivers the facts. The second shows the actions and counts. The third is the forward plan with a tripwire. The fourth states the control. The last offers evidence. If you need to fit a short-form support form, keep the first and third paragraphs and attach the rest.
Bottom line: Five short paragraphs, every number traceable to an attachment, and a tripwire that makes the plan testable.
How should the appeal change by restriction tier?
The same appeal doesn't fit every restriction. The more serious the restriction, the more evidence a reviewer expects and the more the letter must show accountability.
| Tier | Typical trigger | Letter length | Extra evidence to include | Tone |
|---|---|---|---|---|
| Automated warning or pause | One campaign over an internal threshold | Five or six sentences | Bounce counts and confirmation that cleaning is done | Brief and acknowledging |
| Manual compliance review | A spike, or an imported list | Full template | Full suppression and verification summary | Factual and detailed |
| Suspension with conditions | Bounces plus complaints or spam-trap hits | Full template plus a complaint breakdown | Consent records and complaint analysis | Accountable and specific |
| Termination review | Purchased or scraped lists, or repeat offences | Often a different conversation | Consent evidence, which may decide the outcome | Candid, with a clear change of practice |
For lighter tiers, a short letter works best. Over-explaining an automated warning can make the sender look more worried than the situation warrants. For heavier tiers, the quality of your consent evidence often decides the outcome, as covered below.
Bottom line: Match the letter's depth to the tier, and expect termination reviews to hinge on consent.
How do you build the evidence pack and draft the appeal?
Follow these steps in order. For a list of tens of thousands of contacts, the process often fits into an afternoon, though larger files take longer to verify.
- Copy the notice into a document. Underline the metric, the campaign name and the date. Your letter has to answer that specific problem.
- Pull the campaign report. Record total messages sent, hard bounces, soft bounces, complaints and unsubscribes. Calculate each rate against the same denominator.
- Export your suppression list. Save a local copy with a reason code for each address, so you can show what was removed and why.
- Export your full sending list as CSV. Include the email column and any engagement fields, such as last open, last click, signup date and source. Excel works too.
- Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, each list can hold up to 25,000 emails, so split larger files first. Standard verification is unlimited on every plan, with no per-email fees, so re-running a corrected file costs nothing extra.
- Read the three buckets. Valid addresses are safe for your first sends. Invalid addresses are removed and suppressed. Risky addresses include catch-all domains, which accept every address, so a specific mailbox can't be confirmed. Learn how these results are handled on the Catch-all email verification page. For a spot-check of one high-value contact, use the Free email checker.
- Export the summary as CSV, Excel or JSON, and save it with the date. On Pro, results are kept for 30 days, so don't rely on the platform to hold them for you.
- Re-import only Valid contacts as a new segment. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this is an export-and-import step. If you'd rather automate it, a email verification API and automation workflow can call the Email verification API from your own scripts. API access is included on Pro, which covers 100,000 emails a month.
- Draft the letter using the template, then run a traceability check. For every number, point to the file you will attach. If you can't, remove the claim.
If you haven't set up an account yet, you can sign up and run the first list before you draft anything. The Free plan's 25 lists a month of up to 150 emails each is enough to test the workflow on a sample.
Bottom line: Export, verify, save the summary within the retention window, re-import only Valid contacts, and cut any number you can't trace to an attachment.
What does a worked appeal look like with real numbers?
This example is illustrative. The arithmetic and plan limits are real, but the verification results are hypothetical.
The situation: A B2B company with 72,400 contacts sent one campaign to the full list. It recorded 1,880 bounces: 1,540 hard bounces and 340 soft bounces that failed on the same campaign.
Step 1: calculate the overall rate.
1,880 ÷ 72,400 = 2.6% overall bounce rate
Step 2: segment the rate to find the cause. This step makes the letter far stronger. Bounce spikes often concentrate in one source, and showing that the rest of the list is healthy proves the problem is contained.
The company had imported 18,000 legacy trade-show leads the week before the send. Of the 1,880 bounces, 1,410 came from that import.
Imported segment: 1,410 ÷ 18,000 = 7.8%
Rest of list: 470 ÷ 54,400 = 0.9%
The rest of the list was healthy. The problem was one import, and the letter says so.
Step 3: clean. Remove the 1,880 bounced addresses, leaving 70,520. Remove 41 complaints, leaving 70,479 contacts to verify.
Step 4: split for the Pro list limit. Each list can hold up to 25,000 emails on Pro, so the file is uploaded as three lists:
25,000 + 25,000 + 20,479 = 70,479
Step 5: spend deep verifications where the risk is. Pro includes 25,000 deep verifications a month. The company used them on the 16,590 remaining imported contacts (18,000 minus 1,410), since that was the highest-risk segment. Standard verification covered the full list.
Step 6: read the results. Hypothetical outcome:
| Bucket | Count | Share | Action |
|---|---|---|---|
| Valid | 61,200 | 86.8% | Used for re-entry |
| Risky | 6,190 | 8.8% | Held back until the main list is stable |
| Invalid | 3,089 | 4.4% | Removed and suppressed |
61,200 + 6,190 + 3,089 = 70,479 ✓
Step 7: cost. One Pro month is $29, or $25 a month on annual billing. For how verification pricing is structured more generally, see email verification pricing.
Step 8: build the re-entry calendar. Each send has a ceiling, and the first one is deliberately small:
| Day | Audience (Valid only) | Volume | Bounce ceiling | Maximum bounces |
|---|---|---|---|---|
| 1 | Opened in the last 30 days | 4,000 | 0.5% | 20 |
| 4 | Opened in the last 90 days | 12,000 | 1% | 120 |
| 10 | Remaining engaged Valid contacts | 25,000 | 1% | 250 |
| 17 | Remaining Valid contacts | 20,200 | 1% | 202 |
4,000 + 12,000 + 25,000 + 20,200 = 61,200 ✓
The appeal excerpt for this case:
On 3 March, our campaign to 72,400 contacts recorded 1,880 bounces, a 2.6% bounce rate. 1,410 of those bounces came from an import of 18,000 legacy trade-show leads that we had not verified. The rest of the list ran at 0.9%. We have suppressed the bounced addresses and verified the remaining 70,479 contacts: 61,200 are Valid, 6,190 are Risky and 3,089 are Invalid, which we have removed. Day 1 sends to 4,000 contacts with a 0.5% ceiling (20 bounces). If any send exceeds its ceiling, we will pause and notify you before the next send.
The letter doesn't defend the import, and it doesn't ask for the full list to resume quickly. The restraint is part of the argument.
Bottom line: Segment the bounce rate to isolate the cause, show the arithmetic, and make the first send small enough that a miss is cheap.
What should you do after you send the appeal?
Reply in the same thread rather than opening new tickets. Duplicate tickets split the case across queues and make the history harder to follow. Keep a simple appeal log with timestamps, recipients and what you sent, so you can answer follow-ups quickly and accurately.
Don't send any campaign while the review is open, including tests to your main list. Even a small send can produce fresh bounces while the reviewer is watching. If you need to test something, ask the reviewer first.
Plan for silence. Manual reviews commonly take several business days, and some take longer, so don't tie your calendar to a single campaign deadline. When a reviewer asks a follow-up question, answer with the specific artifact requested, such as the suppression CSV or a consent sample, rather than a new explanation. Quick, specific replies tend to matter almost as much as the first letter.
Once the account is reinstated, reputation recovery runs on a separate clock. Inbox placement can lag, as explained in our guide on how long a bad campaign lingers. Put a recurring list maintenance schedule in place now, not after the next spike.
Bottom line: One thread, no sends during review, fast answers to specific requests, and a maintenance schedule in place before reinstatement.
What do you say when a reviewer asks for proof of consent?
Answer with source-level records, not assertions. For each segment, be ready to show the form or source where the contact was collected, the date and time of opt-in, the double opt-in confirmation timestamp if you use one, the consent wording the person saw, and the IP address if you store it. A sample of records is usually more persuasive than a summary.
Verification and consent are different things. A verifier can tell you an address is deliverable, but it can't tell you the person agreed to hear from you. That gap is why email verification compliance and hygiene is a separate discipline from deliverability. For baseline expectations in the United States, the FTC's CAN-SPAM compliance guide is the official starting point.
When you can't prove consent for a segment, don't argue for it. Suppress it and say so. A sentence such as "We cannot evidence opt-in for 4,200 contacts from the 2021 import, so we have suppressed them" is far more credible than a defence of the same contacts. The reasoning is simple: a sender who cuts a segment reduces the risk the reviewer has to model, while a sender who defends it asks the reviewer to accept that risk.
Bottom line: Show records, not reassurance. If you can't evidence consent for a segment, suppress it and say so.
What happens if the appeal is refused?
A refusal isn't always the end. The next move depends on what the reviewer objected to.
| Outcome | Likely reason | Next move |
|---|---|---|
| Asked for more detail | The cause or counts were unclear | Supply the specific evidence requested |
| Reinstated with conditions | The risk is accepted but limited | Accept the cap, and document every send against it |
| Refused on the same list | The list itself is the problem | Re-verify, remove unprovable segments, then appeal again with the new counts |
| Termination | Purchased or scraped data, or repeat offences | Review consent records first, then consider migrating a fully verified list |
Moving to a new provider doesn't fix a list that hasn't changed. Some providers may ask about previous platforms during onboarding, and the same unverified list will reproduce the same spike. Verify and suppress first, then migrate with the suppression history intact.
Bottom line: A refusal usually means the evidence was insufficient or the list is unchanged. Fix the specific objection, or fix the list, before you try again.
Common mistakes that get appeals rejected
- Sending before you're told you can. A resumed campaign during review can turn a warning into a termination.
- Deleting only the addresses that bounced. The rest of the list is still untested, and reviewers know it.
- Writing "we cleaned the list" with no counts. Without numbers, the reviewer has nothing to check.
- Mixing up denominators. A rate calculated against list size but labelled as against sends won't reconcile with the notice.
- Answering a different metric. If the notice cited bounces and you discuss complaints, the reviewer will assume you didn't read it.
- Putting Risky and catch-all addresses in your first wave. They belong at the end of the ramp, after the Valid segments show stable results.
- Losing your suppression history during an export or migration, which forces you to re-learn what you already knew.
- Treating verification as proof of consent. A deliverable address is not an opted-in address.
- Over-promising. Claims such as "zero bounces going forward" can't be proven and become a liability at the next spike.
Bottom line: Most rejected appeals come from sending too soon, claiming without counting, or confusing deliverability with consent.
How we compared (and limitations)
This guide draws on public documentation. It is not based on tests against any ESP's review team.
- Amazon SES's documentation describes a 5% bounce rate as the point where an account goes under review, and 10% as a level that may lead to a pause. We could not confirm equivalent published figures for most other platforms, and some may act at lower levels, especially on a single campaign to an unproven list.
- Google's email sender guidelines advise bulk senders to keep user-reported spam rates below 0.10% and to avoid reaching 0.30%. We recommend a 2% total bounce ceiling for your appeal because it leaves room below the public thresholds we could confirm. We recommend 1% per send for re-entry.
- RFC 3463 defines enhanced SMTP status codes. Hard failures such as 5.1.1 (bad destination mailbox) are the bounces that matter most in an appeal, and 4.x.x codes are transient.
- Unlimited Verifier's plan limits and retention periods come from the product's published facts. The 99.5% deep verification accuracy figure is the company's own stated figure, not an independent benchmark.
Thresholds and review processes vary by platform and change without notice. The worked example uses hypothetical verification results and shows the method, not a predicted outcome. Confirm your own platform's current rules before you send anything. If you're still choosing a verifier, our buyer's checklist for choosing an email verifier and the best email verification tools glossary entry explain the differences that matter for this work.
Bottom line: Treat these figures as a planning baseline, and confirm your platform's current rules before you act on them.
Worked root-cause sentence
We imported 18,000 contacts from a purchased file on March 3 that had never been mailed. Between March 3 and March 10 we sent 42,000 messages and recorded 2,604 bounces (6.2% of attempted sends). We have since suppressed 2,604 hard-bounced addresses, verified the remaining 15,400 contacts with a third-party tool, and will re-enter with a 2,000-recipient engaged segment capped at 1% bounces with an automatic pause if exceeded.
Frequently asked questions
How long should an ESP appeal be?
Aim for roughly 250 to 300 words. Reviewers skim quickly, so a short letter that states the cause, the counts, and the re-entry plan performs better than a long narrative. Attach supporting evidence such as bounce breakdowns and suppression logs instead of pasting them into the body.
How long does an ESP appeal take to get a response?
Response times vary by provider and by whether the case is handled by a first-line reviewer or escalated to a compliance team. Check the provider's published guidance or the suspension notice for any stated timeframe, and plan your re-entry schedule so you are not sending while waiting.
What bounce rate should I target after reinstatement?
Keep bounces well under 2% and set a tripwire at 1% that pauses sending and notifies the provider. Many senders use a lower target for the first campaigns after reinstatement to show a stable trend.
Should I send to my whole list after an appeal is approved?
No. Re-enter with a small, engaged segment, such as recent openers or recent purchasers, and increase volume gradually on a dated calendar. Sending the full list on day one looks like the behaviour that caused the suspension.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent delivery failure, such as a non-existent address or domain, and should be suppressed immediately. A soft bounce is temporary, such as a full mailbox or a server timeout, and is usually retried a limited number of times before suppression.
How do I calculate bounce rate for an appeal?
Divide bounced messages by messages attempted for the same campaign or period, and state that denominator explicitly. Do not divide by total list size unless you say so, because that mismatch is a common reason reviewers cannot reconcile a letter with the sending data.
Should I mention that I bought or scraped the list?
If the list was acquired or scraped, say so plainly in the root-cause sentence and describe what you have stopped doing. Hiding the source makes the appeal less credible, and reviewers often check the import history against what you describe.
Can I reuse the same appeal letter with a different ESP?
You can reuse the structure, but each provider uses its own metrics, thresholds, and terminology. Adjust the letter to match the metric named in that provider's suspension notice and follow its submission instructions.
What if my appeal is rejected?
Read the response for any specific reason, fix the gap it points to, and resubmit with stronger evidence. If the rejection is vague, ask for the specific metric or policy involved before you resend, rather than repeating the same letter.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.