Email Spam Checker

An email spam checker tests a message against the signals spam filters use, authentication, sender reputation, and content, and reports a spam score with the reason for each flag. Palisade's email spam checker, also called a spam tester or email spam test, receives a real email you send and reports what the receiving server saw: SPF, DKIM, and DMARC authentication and alignment, the reputation of the sending IP, and the content of the message. Palisade's spam checker returns a 0 to 100 spam score, a letter grade, and the fix for each flag. Higher is better: 100 means nothing we checked would push the message toward the spam folder.

An email deliverability test, or email deliverability checker, evaluates whether your email setup lets your messages reach recipients' inboxes instead of spam folders. The factors that decide this are sender authentication (SPF, DKIM, DMARC), the reputation of your sending IP and domain, and the content of the message itself. This spam checker is exactly that: send one real email to test email deliverability and it checks all three at once.

Scores run from 0 to 100 and higher is better. 90 to 100 is an A: strong inbox signals. 80 to 89 is a B. 65 to 79 is a C: something needs attention. 50 to 64 is a D: a real risk of filtering. Below 50 is an F. This is not a SpamAssassin score, where lower is better. Here, 100 means nothing we checked would push the message toward spam.

You send any email from the account you want to test (your regular mailbox or your marketing platform) to the unique address we generate. Our receiving server evaluates it exactly the way mailbox providers do on arrival: it records the SPF, DKIM, and DMARC results and alignment, identifies the sending IP and checks its reverse DNS and status on seven major blocklists, and scans the content for common filter triggers. You get a graded report in about thirty seconds.

No, and that is a deliberate choice. Seed-list placement tests show where one message landed at a handful of test mailboxes, a snapshot that changes day to day. This test shows why mail gets filtered: the authentication, reputation, and content signals every receiver evaluates. Those are the causes you can actually fix, and failing authentication is the most common controllable reason this test finds for legitimate email landing in spam.

A real one. If you are diagnosing a newsletter or campaign, send the actual campaign from your email platform so the test sees the same infrastructure, headers, and content your subscribers get. If you are testing your everyday mail, send a normal message from your mailbox. Any subject and any content work: the closer the message is to what you really send, the truer the verdict.

The report lists the exact reasons, ordered by impact. The most common are: DMARC failing or missing, SPF or DKIM passing but not aligned with your From domain, a DMARC policy of p=none (which monitors but blocks nothing), your sending IP appearing on a blocklist, missing reverse DNS, and content flags like a missing List-Unsubscribe header. Each issue in your report maps to a specific fix.

SPF and DKIM failures usually mean a sending service was never added to your DNS records, or the records drifted out of date. Alignment failures mean the domain in those records does not match your From domain. The durable fix is a correct record set plus DMARC reporting so you can see every sender using your domain. Palisade's agent does exactly this: it reads your DMARC reports, finds every sender failing SPF or DKIM, drafts the record fixes, and proposes each policy step toward enforcement. You approve before anything ships.

Yes: free, no signup, no limits that matter for normal use. We also email a copy of the report to the address you sent from, with a link back to your full results, so you can forward it to whoever manages your DNS.