Codenewsletter uses Beehiiv

Codenewsletter uses Beehiiv as their primary email service provider. They rank #681,585 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 85/100).

Marketing ESP

Beehiiv

Total observations4

Active days3

Avg per active day1.3

Last activity📬 Active · yesterday

Cadence~weekly

Interested in using Beehiiv?

Learn about the pros and cons at .

Read the review →

Compare Codenewsletter with another brand:

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

✓

Strong email setup

Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.

85/100

SPF

pass

DKIM

pass

DMARC

pass (reject)

BIMI

none

Unsubscribe

one-click

SPF lookups 2/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 superhuman.ai. Policy p=reject means receivers actively block or quarantine spoofed mail.

SPF alignment: all 4 observed emails use a return-path aligned with codenewsletter.ai (em6050.news.codenewsletter.ai). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 4 observed emails sign with a domain aligned with codenewsletter.ai (news.codenewsletter.ai). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 2 sends).

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 ✓ via SendGrid

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.

SendGrid

Probed: codenewsletter.ai, em6050.news.codenewsletter.ai, news.codenewsletter.ai

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.

Folder	Count	Share
inbox	4	100.0%

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	4		100.0%	0.0%	0.0%

ESP activity over time

Jun 16 – Jun 30, 2026 · 3 days with sends

Last 30d Last 90d

By ESP By inbox/spam

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