See the message. Understand the details.
Email Inspector is a built-in set of email checks beside the message you received. It helps you explore what arrived, understand reported technical observations and decide what to check next. It is not a comprehensive security audit or a deliverability verdict.
A closer look at one test message
The illustration uses fictional data and mirrors the compact inspector workflow. Try each tab to see the kinds of evidence available; nothing is uploaded or scanned here.
Example inspection
Northstar Studio · sign-in email
Reported by the receiving mail system from evidence available with this message.
The receiving system reported that the sending server was permitted for the envelope domain.
The receiving system reported a validated signature for the signing domain.
The receiving system reported alignment with the visible From domain.
Informational observation
Reply-To uses a different domain.
This can be intentional when replies are handled by another service. This observation is informational, not a security failure.
Suggested next check: Confirm that the Reply-To address belongs to your intended support or reply-handling system.
What each tab helps you inspect
Preview
Read the HTML or plain-text message and switch between responsive preview widths. These are useful viewing widths, not Gmail or Outlook emulation.
Details
Review the sender, recipient, Reply-To, received time and available attachment metadata next to the message.
Authentication
See reported SPF, DKIM and DMARC results when the received message contains trustworthy evidence, with plain-English context.
Headers
Read the original message headers in order when you need to follow the route or compare technical identities.
Source
Compare HTML and plain-text source, and download the original .eml file when it is available.
Built-in checks without hidden actions
Responsive viewing widths
Switch widths to find wrapping and layout problems without claiming to reproduce a specific email client.
Attachment context
See available filenames, types and sizes beside the sender details before opening or downloading a file.
External images stay blocked
Remote images do not load until you allow them, so opening a message does not automatically request those resources.
Links can be inspected first
Review link destinations without DemoPost automatically visiting them. You still decide whether a destination is appropriate.
Original message when available
Download the original .eml file for deeper inspection or to share with the team responsible for sending.
Useful in the work you already do
Developers
Compare the visible From address, Reply-To, return path, source and authentication evidence after changing a sender or template.
QA teams
Check that HTML and plain text contain the expected content, links and attachment metadata in a repeatable release test.
Demo teams
Confirm the test message is presentable before a meeting, while keeping deeper evidence nearby if a technical question comes up.
Read results with the right limits
What DemoPost does not do
- Missing evidence is shown as unavailable. It does not prove that authentication failed.
- Messages generated entirely inside a system may not have evidence from an external delivery path.
- Authentication passing does not prove a message is harmless and does not guarantee inbox placement at another provider.
- DemoPost does not currently provide a live DNS configuration checker, malware scanner or comprehensive spam score.
- The authentication checks apply to email. They do not apply to incoming SMS.
Related reading
Inspect your next test message
Start the 7-day trial, send one test email from your application and examine what arrived beside the message.
Try Email for 7 days. Then €19/month, excluding applicable tax. Cancel before your trial ends to avoid the subscription charge.