Pendo uses Marketo for marketing email and Amazon SES for transactional/notifications. They rank #906 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 85/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 DMARC Analyzer (Mimecast). Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: observed emails use a third-party return-path (potomac1050.mktomail.com, amazonses.com) — SPF passes there but doesn't align with pendo.io, so DMARC has to rely on DKIM alignment.
DKIM alignment: all 9 observed emails sign with a domain aligned with pendo.io (hi.pendo.io, pendo.io). DKIM authenticates the visible From — supports DMARC directly.
TLS: 40% TLS 1.3, 60% TLS 1.2 (across 5 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: pendo.io, potomac1050.mktomail.com, amazonses.com, hi.pendo.io
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 | 15 | 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 % |
|---|---|---|---|---|---|
| Marketo | 10 | 100.0% | 0.0% | 0.0% | |
| Amazon SES | 4 | 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 pendo.io has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 199.15.213.54 | potomac1054.mktomail.com |
5 | 1 | Check → |
| 199.15.213.55 | potomac1055.mktomail.com |
4 | — | Check → |
| 199.15.213.56 | potomac1056.mktomail.com |
2 | — | Check → |
| 54.240.48.107 | a48-107.smtp-out.amazonses.com |
2 | 2 | Check → |
| 54.240.48.101 | a48-101.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.48.105 | a48-105.smtp-out.amazonses.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
hi.pendo.io | Marketo 9 | |
pendo.io | Amazon SES 4 Marketo 2 |