Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Thebirdhouse

thebirdhouse.co
🏆Rank N/A 🏷 Food & Beverage

Thebirdhouse uses Beehiiv as their primary email service provider. Their email authentication setup is incomplete (score 58/100). Missing: SPF, DMARC enforcement.

Marketing ESPBeehiiv
Total observations3
Active days2
Avg per active day1.5
Last activity📬 Active · 8 days ago
Cadencealmost daily
Interested in using Beehiiv?
Learn about the pros and cons at .
Read the review →
Compare Thebirdhouse with another brand:

Email setup 58/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.

Setup has gaps
Some authentication is missing or weak — receivers may give less benefit of the doubt.
58/100
SPF
fail
DKIM
pass
DMARC
pass (none)
BIMI
none
Unsubscribe
one-click
SPF lookups 3/10

SPF / DKIM / DMARC above reflect the last 3 emails we've observed. DMARC policy is read live from DNS.

Authentication

DMARC reports sent to thebirdhouse.co. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: all 3 observed emails use a return-path aligned with thebirdhouse.co (em4107.mail.thebirdhouse.co). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 3 observed emails sign with a domain aligned with thebirdhouse.co (mail.thebirdhouse.co). DKIM authenticates the visible From — supports DMARC directly.

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

None — only the primary ESP(s) shown above

Confirmed senders

ESPs 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.

Beehiiv observed

"Observed" pills mean we detected emails from these ESPs, but they don't appear in any SPF record we probed. They may still be properly authorized — sending infrastructure can live on subdomains we haven't seen yet, or use IP-listing instead of include: directives.

Other SPF authorizations

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.

Google Workspace

Probed: thebirdhouse.co, em4107.mail.thebirdhouse.co, mail.thebirdhouse.co

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 2 66.7%
promotions 1 33.3%

Placement by ESP

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 3
66.7% 33.3% 0.0%

ESP activity over time

Jun 22 – Jun 23, 2026 · 2 days with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

2 0 Beehiiv: 1 (2026-06-22)1Beehiiv: 2 (2026-06-23)206/2206/23
Beehiiv

Similar brands using Beehiiv

Sending domains

DomainESPs detectedDelivery (7d)
mail.thebirdhouse.coBeehiiv 3