Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Metabaseapp

metabaseapp.com
🌐Web popularity #117,627 🏷 SaaS 🇺🇸United States

Metabaseapp uses Amazon SES as their primary email service provider. They're the #117,627 most-visited website overall, per Tranco (a web-popularity measure, not an email one). Their email authentication setup is solid (score 85/100). Missing: one-click unsubscribe.

Transactional ESPAmazon SES
Total observations5
Active days3
Avg per active day1.7
Last activity📬 Active · yesterday
Cadence~weekly
Compare Metabaseapp with another brand:

Email setup 85/100

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.

Strong email setup
Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.
85/100
SPF
pass
DKIM
pass
DMARC
pass (reject)
BIMI
none
Unsubscribe
missing
SPF lookups 2/10

SPF / DKIM / DMARC above reflect the last 4 emails we've observed. DMARC policy is read live from DNS.

Authentication

DMARC reports sent to metabase.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 metabaseapp.com, so DMARC has to rely on DKIM alignment.

DKIM alignment: all 5 observed emails sign with a domain aligned with metabaseapp.com (metabaseapp.com). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: modern — 100% TLS 1.3 (across 5 sends).

Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 4 sends).

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

None — only the primary ESP(s) shown above

Confirmed senders

ESPs 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.

Amazon SES ✓ confirmed

Other SPF authorizations

No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.

Probed: metabaseapp.com, amazonses.com

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 5 100.0%

Placement by ESP

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 5
100.0% 0.0% 0.0%

ESP activity over time

Jun 10 – Jun 30, 2026 · 3 days with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

3 0 Amazon SES: 1 (2026-06-10)1Amazon SES: 3 (2026-06-24)3Amazon SES: 1 (2026-06-30)106/1006/1306/1606/1906/2206/2506/2806/30
Amazon SES

Similar brands using Amazon SES

Sending IPs

IP addresses metabaseapp.com has been observed sending from, and where their mail landed in Gmail.

IPHostnameObsPlacementReputation
54.240.8.221 a8-221.smtp-out.amazonses.com 4 3 Check →
54.240.8.51 a8-51.smtp-out.amazonses.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
metabaseapp.comAmazon SES 5