Loopwp 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.
SPF / DKIM / DMARC above reflect the last 4 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to Postmark DMARC. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 14 observed emails use a return-path aligned with loopwp.com (em5548.mail.loopwp.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 10 observed emails sign with a domain aligned with loopwp.com (mail.loopwp.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 7 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: loopwp.com, em5548.mail.loopwp.com, mail.loopwp.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 | 14 | 93.3% |
| promotions | 1 | 6.7% |
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 | 13 | 92.3% | 7.7% | 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 loopwp.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 159.183.140.201 | o169.ptr1700.mail.beehiiv.com |
6 | 3 | Check → |
| 159.183.159.49 | o4.ptr1546.mail.beehiiv.com |
3 | — | Check → |
| 159.183.140.27 | o167.ptr4513.mail.beehiiv.com |
3 | — | Check → |
| 159.183.114.39 | o156.ptr293.mail.beehiiv.com |
1 | — | Check → |
| 149.72.67.64 | o80.ptr4836.mail.beehiiv.com |
1 | — | Check → |
| 159.183.29.70 | o166.ptr78.mail.beehiiv.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
mail.loopwp.com | Beehiiv 16 |