Tldrnewsletter uses Amazon SES as their primary email service provider. They rank #260,217 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 95/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 2 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to cloudflare.net. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: 94% of observed emails use an aligned return-path (dailyupdate.tldrnewsletter.com); the rest use third-party paths (netcorecloud.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 40 observed emails sign with a domain aligned with tldrnewsletter.com (tldrnewsletter.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 12 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).
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: tldrnewsletter.com, dailyupdate.tldrnewsletter.com, netcorecloud.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 | 54 | 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 | 53 | 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 tldrnewsletter.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 54.240.77.23 | a77-23.smtp-out.amazonses.com |
5 | 2 | Check → |
| 54.240.77.26 | a77-26.smtp-out.amazonses.com |
5 | — | Check → |
| 54.240.77.25 | a77-25.smtp-out.amazonses.com |
5 | — | Check → |
| 54.240.77.27 | a77-27.smtp-out.amazonses.com |
4 | — | Check → |
| 54.240.123.112 | a123-112.smtp-out.amazonses.com |
4 | 1 | Check → |
| 54.240.123.115 | a123-115.smtp-out.amazonses.com |
4 | — | Check → |
| 54.240.123.113 | a123-113.smtp-out.amazonses.com |
4 | — | Check → |
| 54.240.123.117 | a123-117.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.123.116 | a123-116.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.38.251 | a38-251.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.77.24 | a77-24.smtp-out.amazonses.com |
3 | — | Check → |
| 54.240.77.28 | a77-28.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.123.114 | a123-114.smtp-out.amazonses.com |
2 | — | Check → |
| 54.240.38.253 | a38-253.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.38.252 | a38-252.smtp-out.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
tldrnewsletter.com | Amazon SES 54 |
