Supersend uses SendGrid as their primary email service provider. We've also observed sends via Amazon SES. Email goes out from 3 different subdomains. Their email authentication setup is good (score 80/100). Missing: one-click unsubscribe.
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.
DMARC reports sent to supersend.io. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: all 17 observed emails use a return-path aligned with supersend.io (em1366.support.supersend.io, em7028.notifications.supersend.io, bounce.supersend.io). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 13 observed emails sign with a domain aligned with supersend.io (support.supersend.io, notifications.supersend.io, supersend.io). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 6 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Amazon SES 3ESPs 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: supersend.io, em7028.notifications.supersend.io, em1366.support.supersend.io, em2304.supersend.io, bounce.supersend.io, support.supersend.io, notifications.supersend.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 | 22 | 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 % |
|---|---|---|---|---|---|
| SendGrid | 16 | 100.0% | 0.0% | 0.0% | |
| Amazon SES | 3 | 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 supersend.io has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 159.183.224.104 | s.wfbtzhsv.outbound-mail.sendgrid.net |
5 | Check → |
| 149.72.126.143 | s.wrqvtzvf.outbound-mail.sendgrid.net |
5 | Check → |
| 149.72.123.24 | s.wrqvtbkv.outbound-mail.sendgrid.net |
3 | Check → |
| 54.240.42.184 | a42-184.smtp-out.amazonses.com |
3 | Check → |
| 149.72.120.130 | s.wrqvtvvn.outbound-mail.sendgrid.net |
2 | Check → |
| 159.183.224.105 | s.wfbtzhsw.outbound-mail.sendgrid.net |
2 | Check → |
| 149.72.154.232 | s.wrqvwxzv.outbound-mail.sendgrid.net |
1 | Check → |
| 54.240.61.167 | a61-167.smtp-out.us-west-2.amazonses.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) |
|---|---|---|
support.supersend.io | SendGrid 9 | |
notifications.supersend.io | SendGrid 8 | |
supersend.io | Amazon SES 3 SendGrid 1 |
