Tabella uses Braze for marketing email and Amazon SES for transactional/notifications. We've also observed sends via 3 other providers: Customer.io, SendGrid, Marketo. Their email authentication setup is incomplete (score 50/100). Missing: DMARC, DMARC enforcement. 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 3 emails we've observed. DMARC policy is read live from DNS.
Multiple DMARC records published — receivers apply no DMARC at all (RFC 7489). The domain is effectively unprotected until the duplicate record is removed.
SPF alignment: observed emails use a third-party return-path (amazonses.com) — SPF passes there but doesn't align with tabella.app, so DMARC has to rely on DKIM alignment.
DKIM alignment: 85% of observed emails sign with an aligned DKIM key (tabella.app); the rest sign with third-party keys (amazonses.com) where DMARC has to rely on SPF alignment.
TLS: 50% TLS 1.3, 50% TLS 1.2 (across 12 sends).
Delivery (last 7 days): 0% under 10 seconds, 0% over 1 minute (across 2 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Intercom 2 Customer.io 1 SendGrid 1 Marketo 1ESPs 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: tabella.app, amazonses.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 | 29 | 96.7% |
| spam | 1 | 3.3% |
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 | 14 | 92.9% | 0.0% | 7.1% | |
| Braze | 3 | 100.0% | 0.0% | 0.0% | |
| Customer.io | 1 | 100.0% | 0.0% | 0.0% | |
| Intercom | 2 | 100.0% | 0.0% | 0.0% | |
| Marketo | 1 | 100.0% | 0.0% | 0.0% | |
| SendGrid | 1 | 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.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
tabella.app | Amazon SES 15 Braze 3 Intercom 2 Customer.io 1 SendGrid 1 Marketo 1 |