Thread uses Amazon SES as their primary email service provider. We've also observed sends via Resend. Their email authentication setup is solid (score 85/100). Missing: one-click unsubscribe.
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 7 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to onsecureserver.net. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 32 observed emails use a return-path aligned with thread.app (send.updates.thread.app). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 29 observed emails sign with a domain aligned with thread.app (updates.thread.app). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 9 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 3 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Resend 2ESPs 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: thread.app, send.updates.thread.app, updates.thread.app
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 | 35 | 100.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 | 31 | 100.0% | 0.0% | 0.0% | |
| Resend | 2 | 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 thread.app has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 54.240.9.42 | a9-42.smtp-out.amazonses.com |
4 | — | Check → |
| 54.240.14.58 | a14-58.smtp-out.amazonses.com |
4 | — | Check → |
| 54.240.9.40 | a9-40.smtp-out.amazonses.com |
3 | 1 | Check → |
| 54.240.14.59 | a14-59.smtp-out.amazonses.com |
3 | 1 | Check → |
| 54.240.14.44 | a14-44.smtp-out.amazonses.com |
3 | 2 | Check → |
| 54.240.14.55 | a14-55.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.14.43 | a14-43.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.9.115 | a9-115.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.9.67 | a9-67.smtp-out.amazonses.com |
2 | 1 | Check → |
| 54.240.9.38 | a9-38.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.14.42 | a14-42.smtp-out.amazonses.com |
2 | 1 | Check → |
| 54.240.9.75 | a9-75.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.9.63 | a9-63.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.14.57 | a14-57.smtp-out.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
updates.thread.app | Amazon SES 33 Resend 2 |
