Stanmail uses Amazon SES as their primary email service provider. Email goes out from 2 different subdomains. Their email authentication setup is good (score 77/100).
Amazon SESAuthentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.
SPF / DKIM / DMARC above reflect the last 1 email we've observed. DMARC policy is read live from DNS.
DMARC enforced with p=reject — receivers actively reject or quarantine spoofed mail. No aggregate reporting destination configured.
SPF alignment: 50% of observed emails use an aligned return-path (feedback.d.stanmail.io); the rest use third-party paths (red-robot.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 1 observed email sign with a domain aligned with stanmail.io (c.stanmail.io). DKIM authenticates the visible From — supports DMARC directly.
Gmail's own filter showed these warnings to real subscribers in their inbox — independent of SPF/DKIM/DMARC pass/fail status. A consistent pattern often signals reputation issues or brand-impersonation concerns.
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
None — only the primary ESP(s) shown aboveESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.
ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.
Probed: stanmail.io, feedback.d.stanmail.io, red-robot.net, d.stanmail.io, c.stanmail.io
Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.
| Folder | Count | Share |
|---|---|---|
| inbox | 1 | 50.0% |
| spam | 1 | 50.0% |
Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.
| ESP | Emails | Placement | Inbox % | Tabs % | Spam % |
|---|---|---|---|---|---|
| Amazon SES | 2 | 50.0% | 0.0% | 50.0% |
Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.
IP addresses stanmail.io has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 54.240.96.87 | a96-87.smtp-out.us-east-2.amazonses.com |
1 | Check → |
Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
d.stanmail.io | Amazon SES 1 | |
c.stanmail.io | Amazon SES 1 |
