Send Feedback
Report a bug, suggest an improvement, or request a feature. Just describe it — we'll categorize it automatically.
or Ctrl+V to paste
| Date | From | To | Subject | Domain | Status | Verdict | Auth | Score | Time |
|---|---|---|---|---|---|---|---|---|---|
| No emails yet | |||||||||
| Domain | Relay To | Customer | Status | Added | Actions | |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Auto-deleted after 90 days (3-month data-minimization cap).
Ctrl+click rows to select · then batch release
| Date | From | To | Subject | 🌐 | Auth | Score | Reason | Actions |
|---|---|---|---|---|---|---|---|---|
| Loading... | ||||||||
| Customer | Domain | Sender | Recipient | Subject | Size | Age | Error | Actions |
|---|---|---|---|---|---|---|---|---|
| Click "Queue" tab to load | ||||||||
| Status | Count | % |
|---|---|---|
| Loading... | ||
| IP Address | Total | Blocked | Block % |
|---|---|---|---|
| Loading... | |||
| Domain | Total | Blocked | Block % |
|---|---|---|---|
| Loading... | |||
Second-pass Ollama scan of every email. Does not change delivery. Shown here: how it performs, and where it disagrees with the live verdict (live said clean/uncertain, shadow said spam/dangerous — these are the ones worth a human look).
| Time | From | To | Subject | Live | Shadow | Shadow Score | Shadow Reason |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
A 30-second view of your email-attack-surface — who is being targeted, what is leaking, and which platforms your people are exposed to. Metadata-only: we never read message bodies.
Last 30 days. 100 = healthy. Penalties subtracted for spam pressure, auth failures, dangerous mail, and traffic from breached platforms.
Concentration risk — who is the spear-phishing magnet on your team.
| Recipient | Hits | Dangerous | Quarantined |
|---|---|---|---|
| Loading… | |||
Sender domains driving the most rejected/quarantined volume.
| Domain | Attempts | Dangerous | Avg score |
|---|---|---|---|
| Loading… | |||
Companies with a known data breach that emailed your organization in the last 30 days — an awareness view of breached brands in your mail flow (a phishing-impersonation surface, and a hint your users may hold accounts there). Recipients = how many of your users received mail from that domain. This does not mean those users are compromised — to see which of your users actually appear in a breach, use Your Exposed Users below.
| Platform | Severity | Breaches | Most recent | Messages | Recipients |
|---|---|---|---|---|---|
| Loading… | |||||
Your own users whose email address appears in a known data breach — across the entire Have I Been Pwned catalog, not only platforms that recently emailed you. Requires per-user breach checks to be enabled for the customer.
Your regular suppliers, partners and customers whose own domains can be impersonated — no DMARC record, or DMARC set to observation-only (p=none). A fraudster can send email that looks exactly like it comes from them, which is how fake-invoice and banking-change scams work. This shows that these domains CAN be imitated, not that anyone has. You can't fix their DNS — but LastSpam can automatically advise them to (Sender Notices).