Expo Etf uses Iterable for marketing email and Amazon SES for transactional/notifications. Their email authentication setup is solid (score 85/100). We've recorded 1 ESP change since first observing this brand.
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 10 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to expo-etf.com. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: observed emails use a third-party return-path (amazonses.com) — SPF passes there but doesn't align with expo-etf.com, so DMARC has to rely on DKIM alignment.
DKIM alignment: all 25 observed emails sign with a domain aligned with expo-etf.com (editor.expo-etf.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 17 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 10 sends).
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.
No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.
Probed: expo-etf.com, amazonses.com, editor.expo-etf.com
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 | 9 | 36.0% |
| promotions | 15 | 60.0% |
| spam | 1 | 4.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 % |
|---|---|---|---|---|---|
| Iterable | 18 | 11.1% | 83.3% | 5.6% | |
| Amazon SES | 7 | 100.0% | 0.0% | 0.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 expo-etf.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 76.223.141.217 | c141-217.smtp-out.amazonses.com |
5 | — | Check → |
| 54.240.79.153 | a79-153.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.79.9 | a79-9.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.73.35 | a73-35.smtp-out.amazonses.com |
2 | — | Check → |
| 76.223.141.188 | c141-188.smtp-out.amazonses.com |
2 | 2 | Check → |
| 23.251.255.222 | e255-222.smtp-out.amazonses.com |
2 | 2 | Check → |
| 54.240.78.180 | a78-180.smtp-out.amazonses.com |
2 | 2 | Check → |
| 54.240.79.13 | a79-13.smtp-out.amazonses.com |
2 | 1 | Check → |
| 76.223.141.189 | c141-189.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.79.151 | a79-151.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.79.175 | a79-175.smtp-out.amazonses.com |
1 | — | Check → |
| 76.223.141.169 | c141-169.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.78.201 | a78-201.smtp-out.amazonses.com |
1 | — | Check → |
| 23.251.255.208 | e255-208.smtp-out.amazonses.com |
1 | — | Check → |
| 23.251.255.195 | e255-195.smtp-out.amazonses.com |
1 | 1 | Check → |
| 54.240.78.240 | a78-240.smtp-out.amazonses.com |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
editor.expo-etf.com | Iterable 19 Amazon SES 9 |