Futureparty uses Beehiiv as their primary email service provider. Their email authentication setup is solid (score 95/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 dmarcian. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 11 observed emails use a return-path aligned with futureparty.com (em1731.mail.futureparty.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 4 observed emails sign with a domain aligned with futureparty.com (mail.futureparty.com). DKIM authenticates the visible From — supports DMARC directly.
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: futureparty.com, em1731.mail.futureparty.com, mail.futureparty.com
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 | 60.0% |
| promotions | 4 | 40.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 | 60.0% | 40.0% | 0.0% |
Monthly 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 futureparty.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 149.72.136.79 | o22.ptr6458.mail.futureparty.com |
6 | Check → |
| 149.72.145.66 | o23.ptr1124.mail.futureparty.com |
5 | Check → |
Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
mail.futureparty.com | Beehiiv 11 |