Tinyseed uses Mailchimp for marketing email and Amazon SES for transactional/notifications. We've also observed sends via 3 other providers: Bento, Drip, SparkPost. Their email authentication setup is solid (score 95/100). We've recorded 4 ESP changes since first observing this brand.
Amazon SESNon-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.
| HTML builder |
Authentication 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 9 emails 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: all 3 observed emails use a return-path aligned with tinyseed.com (drip.tinyseed.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 31 observed emails sign with a domain aligned with tinyseed.com (tinyseed.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 92% TLS 1.3 (across 12 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 9 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Bento 7 Drip 4 SparkPost 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.
"Observed" pills mean we detected emails from these ESPs, but they don't appear in any SPF record we probed. They may still be properly authorized — sending infrastructure can live on subdomains we haven't seen yet, or use IP-listing instead of include: directives.
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: tinyseed.com, drip.tinyseed.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 | 41 | 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 | 18 | 100.0% | 0.0% | 0.0% | |
| Bento | 5 | 100.0% | 0.0% | 0.0% | |
| Drip | 3 | 100.0% | 0.0% | 0.0% | |
| Mailchimp | 5 | 100.0% | 0.0% | 0.0% | |
| SparkPost | 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 tinyseed.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 168.245.99.76 | o33.sg.m.dripemail2.com |
1 | Check → |
| 168.245.123.156 | o21.sg.m.dripemail2.com |
1 | Check → |
| 168.245.74.76 | o32.sg.m.dripemail2.com |
1 | Check → |
| 168.245.19.191 | o22.sg.m.dripemail2.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) |
|---|---|---|
tinyseed.com | Amazon SES 18 Mailchimp 7 Bento 7 Drip 4 SparkPost 2 |