Loading...
Preparing your workspace
Loading tool...
Please wait.
Free: raw source up to 256 KB. Upgrade for up to 2 MiB.
Test address
—
See how a message is likely to land before you send: paste or upload raw email source for a clear report on domain authentication signals, simple content-risk hints, and copy-friendly summaries. Subscribers can analyze larger single messages and run multi-file batches packaged as one ZIP with per-message results plus a summary file. When you explicitly use the AI Assistant option, you get optional wording suggestions aimed at clearer outreach.
White-Label Platform
Paste a small snippet on your domain, use your branding, and sell to your clients with one subscription and no revenue share.
Learn moreCommon questions about this tool
Use full raw message text with headers and body, or save that source as a small .eml or .txt file for subscriber batch runs. A sample message is available if you want to preview the layout first.
It highlights authentication posture for the visible sender domain, simple content-risk hints from subject and body, and readable summaries so you can tighten structure or tone before send.
Only when you choose that option after review. It suggests alternative subject or body wording to reduce common friction patterns; larger sources and multi-file ZIP exports stay on paid plans.
Paste full raw message text (headers and body), load the sample, or use Send to test: we provision the same disposable inbox style as the Temporary Email tool on ToolGrid. Send from your system to that address, then run the check to analyze the message we received on our MX (SPF uses the real SMTP client IP, plus DKIM and DMARC evaluation). Paste-only mode uses the same engine but SPF is inconclusive without the connecting IP.
The tool parses RFC822, evaluates DKIM signatures and DMARC alignment using standard libraries, evaluates SPF when the SMTP client IP is known (Send to test path), and shows whether common SPF/DMARC TXT records exist for the From domain. It also lists neutral content signals (links, attachments, List-Unsubscribe, bulk precedence). It does not predict Gmail/Outlook placement; that requires provider-specific seed tests or APIs.
The page parses the raw source, runs mail authentication checks (SPF when IP is available, DKIM, DMARC), and fetches public TXT records for the From domain as supplementary hints. A structured content-signals panel summarizes links, attachments, and list headers. Free and paid users get the same evaluation logic; paid tiers raise size limits and add PDF export and batch ZIP.
This tool cannot open your recipients’ spam folders. It helps you spot risky wording and missing or weak domain records before you send. For real placement, use seed inboxes or your provider’s postmaster tools where you are allowed to.
Use the free paste path or Send to test with the smaller limits shown in the UI. Analysis quality matches paid; upgrading increases RFC822 size limits, disposable inbox lifetime for Send to test, optional batch ZIP, and PDF download of the same report object.
This tool no longer shows a single heuristic spam dial. Read the authentication results (SPF/DKIM/DMARC) together with the content signals panel. Those are diagnostic signals only—not a provider inbox score.
In real life, list quality, consent, infrastructure, domain and IP reputation, and engagement all matter. This ToolGrid view summarizes authentication (SPF when IP is known, DKIM, DMARC), optional MX Authentication-Results, public TXT hints for the From domain, and content signals from one message—treat it as one early step in a wider checklist.
When authentication looks wrong or content looks noisy, more mail gets delayed or filtered, so campaigns underperform. A quick pass here catches obvious mismatches between your From domain and published lines before you widen the send.
Fix your real sending setup first—aligned From domain, clean lists, honest subject lines—then export fresh raw source and re-run. After analysis you can optionally use the AI Assistant for softer wording when you choose to run it.
There is no single spam score in this tool. Review DKIM/DMARC/SPF outcomes, the MX Authentication-Results snapshot when you used Send to test, and the content signals (links, attachments, List-Unsubscribe). For real spam-folder behavior you must still use your provider’s tools or seed inboxes where permitted.
This tool reads public TXT records tied to the visible From domain, which is one slice of reputation signaling. It does not show full third-party reputation scores or IP history; pair these hints with your normal postmaster or monitoring tools.
Heavy tracking links or odd redirect patterns can influence how strict filters treat a message. This page counts plain-text links it can see in the pasted body but does not simulate how each provider scores tracking pixels or redirects.
Providers combine content signals, authentication, reputation, and user engagement in ways you cannot see from one paste. Here you see structured content signals, authentication outcomes, and public TXT hints for the From domain—not a provider’s internal scoring.
Export or copy the raw source of your final draft (or use Send to test to mail our disposable inbox), then review authentication, MX Authentication-Results when applicable, and the content signals panel. Adjust the message or DNS at the source, then run again until the report matches your intent.
Common issues include weak or missing authentication records, spammy wording, very high link density, and poor list hygiene. This tool surfaces the first three categories on a static pass so you can fix them before send.
This ToolGrid flow does not query blocklists. It focuses on message parsing and the TXT-style checks shown in the report. Use a dedicated blocklist lookup service if you need realtime blacklist status for your domain or IPs.
Yes. Paste saved raw source or use the server sample and run analyze without sending anything. Sending is optional: use Send to test only when you choose to send mail to the disposable address we show.
Re-run whenever you change templates, domains, or major links, and before large sends. Small copy edits may not need a full pass, but authentication or From-domain changes deserve a fresh check.
Industry benchmarks vary by list type and region, and this tool does not compute a send-time delivery percentage. Use it to reduce obvious risk before you measure real rates in your ESP or postmaster reports after sends.
Public TXT records tell receivers whether you published common sender and receiver policy lines. The tool surfaces whether those lines appear for the From domain you pasted; missing lines are a common reason stricter filters hesitate.
Strong alignment between your From domain, published SPF/DMARC, and valid DKIM signatures helps receivers trust mail. This tool verifies DKIM from the pasted or MX-stored RFC822 when the body matches the signatures, evaluates DMARC alignment from those results, and evaluates SPF only when the SMTP client IP is known (Send to test). Paste-only without IP leaves SPF inconclusive by design.
Yes. Low reputation at the domain or IP level can still filter mail even when one message reads fine. This page only shows message-level clues and those TXT lookups, not your full sending reputation history.
Reputation is tracked over time by providers and often viewed in postmaster dashboards or third-party tools. Use this ToolGrid test for a single-message sanity read, then follow your usual reputation workflow for deeper signals.
Delivery rate usually counts accepted messages versus attempts. Deliverability is the broader idea of reaching the inbox instead of spam or bulk tabs. This tool helps you preview risks before you measure either metric in production.
Verified content & sources
This tool's content and its supporting explanations have been created and reviewed by subject-matter experts. Calculations and logic are based on established research sources.
Scope: interactive tool, explanatory content, and related articles.
ToolGrid — Product & Engineering
Leads product strategy, technical architecture, and implementation of the core platform that powers ToolGrid calculators.
ToolGrid — Research & Content
Conducts research, designs calculation methodologies, and produces explanatory content to ensure accurate, practical, and trustworthy tool outputs.
Based on 2 research sources:
Learn what this tool does, when to use it, and how it fits into your workflow.
This email deliverability test parses RFC822 you control and returns structured authentication results (SPF when the SMTP client IP is known, DKIM verification, DMARC evaluation), published SPF/DMARC TXT hints for the From domain, neutral content signals (links, attachments, List-Unsubscribe, bulk precedence), and a short body preview. Free and paid users share the same evaluation engine; paid tiers raise size limits, add PDF export, batch ZIP, and longer disposable inboxes for Send to test. It does not predict Gmail or Outlook placement—that requires provider seed tests or placement APIs.
Teams sometimes follow raw review with a focused single-address verification step when mailbox-oriented signals are still open questions.
Send to test provisions the same disposable inbox style as ToolGrid Temporary Email on a ToolGrid domain. Send from your mail system, then run the check to analyze the message stored on ToolGrid MX (SPF uses the real connecting IP). Paste-only mode uses the same engine; SPF is inconclusive without that IP.
Plain address strings without headers can still pass through a separate format-focused validation pass before you export a full raw message.
The page saves time by replacing a scattered manual routine—open headers, count links, look up domain records, reason about SPF/DKIM/DMARC—with one pass. It fits marketers, support staff, and developers who need a fast sanity read before a wider send.
Many teams first ask why email deliverability is important: if authentication and content look risky, more mail gets filtered or delayed. This tool does not promise inbox placement; it summarizes authentication and content signals you can act on before you widen a send.
There is no single “secret inbox score” here. Read SPF, DKIM, and DMARC rows together with the content signals panel and, when applicable, the MX Authentication-Results snapshot captured at receipt on ToolGrid.
Raw source is the block of headers and body you export from a mail client or sending tool. The hard part by hand is staying consistent across drafts. An email deliverability tester view like this keeps the same steps each time.
When you need more record types than the quick TXT slice shown here, a structured record query on the same hostname can extend the picture in the same developer utilities grouping.
Before a campaign: use check email deliverability style review on an exported draft so authentication lines match the domain you intend to send from.
Odd-looking hostnames in the From line can be double-checked with a hostname rule pass so you do not misread authentication results.
Learning: how to test email deliverability free on the small limit means students can repeat runs on the bundled sample without paying.
Debugging: a developer pastes a failing message to see whether the plain body, link density, or missing records line up with what support suspects.
Batch subscribers: compare several saved .eml files in one zip when QA needs the same packaging for tickets.
The parser reads standard mail shape, pulls the first From address and domain, counts links, notes attachments and HTML parts, and builds the preview window. Authentication uses industry-standard evaluation (mailauth): DKIM signature verification, DMARC policy and alignment, and SPF when the client IP and envelope context are available. Published TXT checks show whether typical SPF and DMARC records exist for the From domain.
Free posts go to the small-cap Next.js analyze route; paid single posts use the larger-cap backend route; batch uses multipart upload and returns a zip stream; PDF export is paid-only but uses the same report JSON.
Rows of sender domains meant for wider trust scoring can be compared in a structured sender-domain review when that workflow fits the same planning stage.
| Mode | What you supply | Typical limit |
|---|---|---|
| Free single paste | One raw string in JSON | About two hundred fifty six thousand characters |
| Paid single paste | One raw string on the premium route | About two million characters |
| Paid batch | Up to five .eml or .txt files | About two megabytes per file and about eight megabytes combined |
For how to verify email deliverability before sending, paste the draft you plan to send (or use Send to test), confirm authentication rows and published TXT hints look aligned with your intent, and read content signals—not as a single yes-or-no verdict.
If you wonder how to test if emails go to spam across every mailbox, you still send controlled tests to seed accounts when your policy allows. This tool does not open recipients’ spam folders.
Guides on how to check email domain reputation in the deep sense (full history, third-party scores) still point you to reputation vendors or postmaster tools. This page still helps with how to check email domain reputation at the basic TXT-record level shown in the report.
Readers also ask how to check email sending reputation beyond this page; transport history and IP or domain reputation live in postmaster tools. Use this report for message-level clues and alignment of visible From with published lines.
Remember what affects email deliverability spans list quality, consent, infrastructure, and engagement. This tool covers a narrow slice—authentication evaluation, content signals, and TXT hints—so you know what it does not replace.
After fixes, how to improve email deliverability means updating configuration and content in your real sending stack, then exporting fresh raw source and running again.
The question how to check if my email is marked as spam usually needs provider dashboards and seed tests, not one paste alone. Use this page first to remove obvious authentication gaps and noisy content patterns.
Treat this page as a narrow email reputation checker step for message-level clues only, not a wholesale domain-risk product.
Permission first: only analyze mail you own or are explicitly allowed to review.
We’ll add articles and guides here soon. Check back for tips and best practices.
Summary: See how a message is likely to land before you send: paste or upload raw email source for a clear report on domain authentication signals, simple content-risk hints, and copy-friendly summaries. Subscribers can analyze larger single messages and run multi-file batches packaged as one ZIP with per-message results plus a summary file. When you explicitly use the AI Assistant option, you get optional wording suggestions aimed at clearer outreach.
