Heynews uses Customer.io for marketing email and Amazon SES for transactional/notifications. Email goes out from 3 different subdomains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.
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.
DMARC reports sent to dmarcinput.com. Policy
p=none is monitor-only — receivers won't act on spoofing yet.
SPF alignment: 50% of observed emails use an aligned return-path (cio109566.m.heynews.co); the rest use third-party paths (heybe.ai) where DMARC has to rely on DKIM alignment.
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: heynews.co, heybe.ai, cio109566.m.heynews.co, m.heynews.co, mail.app.heynews.co, mail.heynews.co
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 | 6 | 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 % |
|---|---|---|---|---|---|
| Customer.io | 1 | 100.0% | 0.0% | 0.0% | |
| Amazon SES | 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.
IP addresses heynews.co has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 159.112.253.46 | v546.v59719d68.use4.send.mailgun.net |
2 | Check → |
| 23.251.226.5 | e226-5.smtp-out.us-east-2.amazonses.com |
1 | Check → |
| 159.112.243.122 | v5122.v5be21903.use4.send.mailgun.net |
1 | Check → |
| 23.251.226.1 | e226-1.smtp-out.us-east-2.amazonses.com |
1 | Check → |
| 159.112.241.119 | v5119.v5c4dda55.use4.send.mailgun.net |
1 | Check → |
Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
m.heynews.co | Customer.io 3 | |
mail.app.heynews.co | Amazon SES 2 | |
mail.heynews.co | Customer.io 1 |