Your score moves while the email doesn't
SpamAssassin rules change, blocklists add and drop entries, and your domain keeps ageing. The score you cleared last quarter is not the score you have today, even if nobody touched the template.
Capture your email once and Unspam re-sends it from your own sending identity on a cadence you pick, then scores it out of 100 and emails you the result. It is recurring spam testing that catches a score drop the week it happens, not after the campaign underperforms.
SpamAssassin rules change, blocklists add and drop entries, and your domain keeps ageing. The score you cleared last quarter is not the score you have today, even if nobody touched the template.
A new subject line, a swapped link, one more image. Each edit can move content quality without anyone re-running the test, and the drop only surfaces in the campaign numbers.
One run tells you where you stand for one send. It cannot show authentication quietly degrading over three weeks, which is how most spam problems actually start.
A manual check only helps when someone runs it. Between campaigns nobody does, and the send you skip is the one that goes out carrying a rule you never saw fire.
Each completed run scores your email from 0 to 100 and bands it Strong, Good, Medium risk, or High risk, then splits that score into three pillars: authentication, sender reputation, and content quality. A critical authentication failure drops the run to High risk on its own, so a broken signature cannot hide behind good content.
The sender reputation pillar re-checks your domain and sending IP against blocklists on every completed run, alongside domain age and domain suffix. A fresh listing shows up as a score drop you can date, instead of arriving as a support ticket weeks later.
Most spam checkers score one paste and forget it. Unspam pins one email and re-scores it like a regression test.
Forward the email a single time. Unspam stores that exact message and re-sends it on every scheduled run, so there is no snippet to paste and no test to remember.
Each run goes out through a sending account you connect over SMTP, so the score reflects your own domain, your own authentication, and your own reputation rather than an anonymous relay.
Run daily, weekly, monthly, or only on the specific weekdays that match your calendar. The schedule is set per test, with a start date and time you choose.
Choose an email on every run so the result reaches you without opening the dashboard. Alerts go to your account email with a link to the full report.
Authentication, sender reputation, and content quality each carry their own percentage and points earned, so you can see which part of the setup moved instead of guessing from a single total.
Every completed run is plotted on a dated chart across 7, 30, or 90 days, or a range you set. Click any point to open that run's full report.
Each run has a public link anyone can open without an account, so a teammate, a client, or your boss sees the proof without a login.
Switch alerts from every run to a spam score percentage you choose, so monitoring stays quiet while the setup is healthy and only reaches you when a send drifts past the line.
Start a test and Unspam gives you a private inbox address. Forward the exact email you want watched, and we capture it to re-use on every run.
Pick the mailbox Unspam should send the recurring test from, connected once over SMTP. Your real sending identity is what gets scored, so the result matches what your recipients receive.
Choose daily, weekly, monthly, or specific days of the week, then set the date and time the first run goes out. Name each test after the flow it covers.
Unspam re-sends and re-scores on schedule, building a dated score history. The result lands in your inbox after each run. Pause, resume, or trigger an extra run at any time.
A one-off check answers where your email stands right now. A recurring one answers the question that actually costs money: is the score holding, and which pillar moved?
Set a weekly run on your main template so the score is verified automatically, instead of depending on someone testing before a send goes out.
Schedule a run on each critical message: reset, receipt, confirmation. These templates change rarely, which is exactly why nobody thinks to re-test them after an authentication change.
The sender reputation pillar re-checks your domain and IP on every run, so a new listing shows up as a dated score drop rather than at the next campaign.
After repairing SPF, DKIM, or DMARC, keep the test running so you can watch the authentication pillar recover and stay recovered, not just pass once.
Run one automatic spam test per domain in the same workspace. Each test is named, so you know which domain moved without opening them one by one.
Every completed run is logged with its date, score, and pillar breakdown, so you have a real trend to hand a client instead of a one-off screenshot.
Figures from Unspam's live deliverability benchmark, the same checks your scheduled run is graded against.
Connect a sending account for every domain you send from, at no extra cost, then pick a cadence (daily, weekly, monthly, or specific days of the week) and the time each run goes out. On every run Unspam re-sends your exact email, scores it, and emails you the result, with no snippet to paste and no test to remember. It is regression testing for your email.
How scheduled spam testing works, and how it differs from a single spam check.
It is a spam test that runs on a schedule instead of on demand. You capture an email once, pick the days and the time, and Unspam re-sends and re-scores it on every run, recording the score over time. Think of it as a recurring email spam test that watches for a score drop so you do not have to remember to check.
A one-off spam check scores a single message once. An automatic spam test turns that same check into a recurring job: capture the email once, set a cadence, and Unspam re-sends and re-scores it on schedule, building a score history instead of a single snapshot.
You connect a sending account over SMTP, the mailbox the recurring test should send from, and capture the email you want watched by forwarding it to a private address we give you. On each scheduled run, Unspam sends that email from your account and scores what arrives. Because every run is a real send from your own sending identity, the result reflects what your recipients actually get.
Each completed run scores your email from 0 to 100 across three pillars. Authentication covers SPF, DKIM, DMARC, reverse DNS, List-Unsubscribe, and BIMI. Sender reputation covers domain and IP blocklists, domain age, and domain suffix. Content quality covers HTML best practice, subject line, accessibility, broken links, spam wording, shortened URLs, and the SpamAssassin result. Each pillar reports its own percentage and the points it earned.
Most teams run a weekly test on their main template, plus a run after any change to content, authentication, or sending setup, the moments a score tends to move. Because each test carries its own cadence, you can match the schedule to how often that message actually sends.
Each test carries its own trigger. Choose an email on every run, or set a threshold so routine runs stay quiet. Alerts go to your account email with a link to the full report.
Yes, on completed runs and on plans that include technical details. Each run shows the sending address, sender IP, and sender host, the full list of headers, and downloads for the raw message and its headers, so you can confirm exactly what left your infrastructure.
No. They answer different questions, and both can run on a schedule. An automatic spam test scores one message for authentication, reputation, and content. Automatic inbox placement seeds your email to real mailboxes and reports where it landed at each provider. A good score does not guarantee inbox placement, but placement problems are often explained by the score.
There is nothing to integrate. You connect a sending account over SMTP and set the schedule inside your Unspam account. Unspam does not plug into your ESP's API and does not need access to your campaigns.
Yes. Every run has a public link anyone can open without an account, so a teammate, a client, or your boss can read the score and its breakdown without a login.
They are two views of one idea. Deliverability Monitoring is the outcome: recurring checks with alerts when something slips. An automatic spam test is one of the two mechanisms that produce it, alongside automatic inbox placement.
No. Unspam does not warm up domains, does not send your campaigns, and is not an ESP. It scores your email on a schedule so you know when to act. The fixes (authentication, list hygiene, content) happen in your own sending stack. For a manual baseline, an email health check reviews authentication and reputation in one pass.
Capture your email once, pick the days and the time, and let Unspam score it and email you the result. Start free, no credit card.