Heybe uses Beehiiv as their primary email service provider. Their email authentication setup is good (score 80/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.
DMARC reports sent to dmarcinput.com. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: all 16 observed emails use a return-path aligned with heybe.ai (em1208.news.heybe.ai). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 13 observed emails sign with a domain aligned with heybe.ai (news.heybe.ai). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (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: heybe.ai, em1208.news.heybe.ai, news.heybe.ai
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 | 13 | 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 % |
|---|---|---|---|---|---|
| Beehiiv | 10 | 100.0% | 0.0% | 0.0% |
Weekly 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 heybe.ai has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 159.183.29.70 | o166.ptr78.mail.beehiiv.com |
10 | Check → |
| 159.183.140.223 | o168.ptr7383.mail.beehiiv.com |
5 | Check → |
| 159.183.140.201 | o169.ptr1700.mail.beehiiv.com |
2 | Check → |
| 159.183.140.172 | o170.ptr9231.mail.beehiiv.com |
1 | Check → |
| 159.183.140.157 | o171.ptr9046.mail.beehiiv.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) |
|---|---|---|
news.heybe.ai | Beehiiv 21 |