message delivered

Meet beehiiv Hex: a faster sending engine.

Wed, Nov 11 · 9:06am ET Product Launches

Sent with Beehiiv Sends about every 2 weeks All facts

Beehiiv introduces beehiiv Hex, its own email sending engine, built for top newsletters. Beehiiv Hex promises faster sends, better inbox placement, and expert support. It runs on Beehiiv's own MTA and IPs, sending over 137 million emails daily.

What the raw message shows

From the headers

Sent with: Beehiiv See it in the headers

Across Beehiiv's email

Sends: About every 2 weeks
DMARC: Enforced, reject
Mail failing authentication is refused.

The copy

579 words · about 2 min to read · 2 buttons

Nearly two years ago, we decided we didn’t want to rent our email infrastructure like the rest of the industry.

So we started building our own.

Introducing beehiiv Hex: our own email sending engine, built for the world’s best newsletters. It runs on our own MTA, from IPs we own and operate, and already sends 137M+ emails every day.

Here’s what it means for you:

⚡ Faster sends

📬 Better inbox placement

🧠 Experts behind every send

🪄 Zero setup

Let’s dive in 👇

Your newsletter is your business. We didn’t want the most important part of it, getting to the inbox, to depend on someone else.

Why we built our own sending engine

Most email platforms don’t actually send your email. When you hit send, they hand the heavy lifting to a third-party sender that’s also sending for thousands of other companies, including plenty of spammers.

That matters because inbox providers judge your email partly by who it’s sent alongside. Your newsletter gets lumped in with the rest of the internet, so someone else’s bad behavior can push you toward the spam folder.

We saw it firsthand: variable sends, and results that weren’t as good as they should be.

So we decided to own our email infrastructure end to end. It’s faster, more reliable, and shared only with the top 1% of senders: the best newsletters in the world.

With beehiiv Hex, we own the path to the inbox. The IP addresses, the servers, the sending reputation, and the team who runs it.

When something changes, we adjust. No ticket to a third party, no waiting in someone else’s queue.

It keeps getting better. We tune beehiiv Hex every week, so every send can benefit.

You don’t have to think about it. You write, you hit send. We handle the rest.

This is our way of giving you the best shot at high deliverability.

Button Take the full tour

Say you run a financial markets newsletter, and something big happens at 6am. You want your take in readers’ inboxes before they’ve opened another app.

beehiiv Hex sends up to 3.7M emails a minute, 68% more than our previous setup. A send to 1M subscribers goes out in about 16 seconds.

Your first reader and your millionth get it at basically the same time.

The small emails matter too. When someone subscribes, their welcome email now goes out in 1.8 seconds at the median, about 3× faster than before. It’s there before they’ve closed the tab.

Button See the speed numbers

Speed doesn’t matter if the email never lands. So here’s how beehiiv Hex is doing:

99.1% of emails sent on beehiiv Hex are accepted by inbox providers. Not to mention, sends on beehiiv Hex average a 43.3% open rate.

You don’t have to take our word for it, either.

In EmailTooltester’s independent Email Detective data, beehiiv ranks #1 of 7 platforms for landing in Gmail’s Primary tab.

A few reasons why:

beehiiv is built for newsletters. Links in your posts get short tracking links, so long posts are lighter and far less likely to get clipped in Gmail.

Every inbox gets its own playbook. beehiiv Hex paces each provider differently and eases off the moment one pushes back, so your send keeps moving.

You’re in good company. Our team screens out purchased lists and complaint spikes before they can affect anyone’s sends.

And yes, open and click tracking work on every send, so your analytics stay exactly where they are.

The words as text: what a screen reader can follow, and all there is when images don't load.

What the headers say

Read from the message's own headers, as it arrived.

Came from

bh186-40.smtp-out.beehiivmail.net · 69.67.186.40

Beehiiv's sending servers

SPF

Pass for bh.mail.beehiiv.com

DKIM

Pass signed by bhmta.beehiiv.com
Pass signed by mail.beehiiv.com

DMARC

Pass for mail.beehiiv.com

Policy: reject

Unsubscribe

One-click

Meets the Gmail and Yahoo rule for bulk senders.

Complaints

Feedback loop set up

Mailbox providers can report spam complaints straight back to the sender.

Show all 26 headers

As received, minus the delivery side: the archive's own addresses show as [recipient], its mail servers as [receiver], signatures are left out and unsubscribe links trimmed to their host.

Route

Received: from bh186-40.smtp-out.beehiivmail.net (69.67.186.40) by [receiver] (cloudflare) id 664UeU13Dee9 for <[recipient]>; Wed, 11 Nov 2026 14:06:14 +0000
Received: from mail.beehiiv.com by bhmta(mta18) with HTTP id <1d9738e1ddd911f1b8690eae6b47d549> for <[recipient]>; Wed, 11 Nov 2026 14:06:39 +0000

Authentication

Received-SPF Authentication result: pass ([receiver]: domain of [recipient]@bh.mail.beehiiv.com designates 69.67.186.40 as permitted sender) receiver=[receiver]; client-ip=69.67.186.40; envelope-from="[recipient]@bh.mail.beehiiv.com"; helo=bh186-40.smtp-out.beehiivmail.net;
Authentication-Results Authentication result: [receiver]; dkim=pass header.d=bhmta.beehiiv.com header.s=bh header.b=nKrNure/; dkim=pass header.d=mail.beehiiv.com header.s=bh header.b=tYYxXaMM; dmarc=pass header.from=mail.beehiiv.com policy.dmarc=reject; spf=none ([receiver]: no SPF records found for [email protected]) smtp.helo=bh186-40.smtp-out.beehiivmail.net; spf=pass ([receiver]: domain of [recipient]@bh.mail.beehiiv.com designates 69.67.186.40 as permitted sender) smtp.mailfrom=[recipient]@bh.mail.beehiiv.com; arc=none smtp.remote-ip=69.67.186.40

Platform

X-BmtaRef: eyJfQF8iOiJcXF8vIiwicmVjaXBpZW50IjoiYmVlaGlpdkBpbmJveGFyY2hpdmUub3JnIiwieF9 hZ2dyZWdhdGlvbl9pZCI6bnVsbCwieF9hZ2dyZWdhdGlvbl90eXBlIjpudWxsLCJ4X2lwX3dhcm 11cF9zY2hlZHVsZV9zdGFnZV9pZCI6bnVsbCwieF9saXN0X2lkIjoiYThlODhmMzgtMWJmNi00Y mFkLTgxNTQtMmM4OTdmZTUxMjUyIiwieF9tZXNzYWdlX3NlbmRfaWQiOm51bGwsInhfbWVzc2Fn ZV90eXBlIjpudWxsLCJ4X25ld3NsZXR0ZXJfbGlzdF9pZCI6bnVsbCwieF9wb3N0X2lkIjoiZDl lZWEzNTItYWJmMy00ODNmLWEyZGYtYTdhZTdhNzc1ZTBhIiwieF9zZW5kYWJsZV9pZCI6bnVsbC wieF9zZW5kYWJsZV9zdWJ0eXBlIjpudWxsLCJ4X3NlbmRhYmxlX3R5cGUiOm51bGwsInhfc3Vic 2NyaWJlcl9pZCI6ImNlNWEzZDNkLTM2ZTAtNDk3MS04ODY0LWFjNzA3NzA4ZjQzYiIsInhfd2Fy bXVwX3NjaGVkdWxlX3N0YWdlX2lkIjpudWxsfQ==
X-Batch-Id: eef8573c-d87b-4b31-8878-7bd8f7f02d9c
X-Subscriber-ID: ce5a3d3d-36e0-4971-8864-ac707708f43b
X-Subscription-ID: 1166737569
x-beehiiv-ids Identifies Beehiiv: {"account_name":"https://product.beehiiv.com/","campaign_id":"d9eea352-abf3-483f-a2df-a7ae7a775e0a","category":"newsletter","email_generated_at":1794405942,"user_id":"a8e88f38-1bf6-4bad-8154-2c897fe51252"}
x-beehiiv-type Identifies Beehiiv: newsletter
x-list-id: a8e88f38-1bf6-4bad-8154-2c897fe51252
x-list-owner: <mailto:[email protected]>
x-newsletter: https://product.beehiiv.com/p/meet-beehiiv-hex
x-newsletter-id: https://product.beehiiv.com/
x-newsletter-signup: https://product.beehiiv.com/subscribe

Unsubscribe and feedback

Feedback-ID: d9eea352-abf3-483f-a2df-a7ae7a775e0a:newsletter:a8e88f38-1bf6-4bad-8154-2c897fe51252:287f8604bf6656d
List-Unsubscribe: <mailto:…@unsub.beehiiv.com>, <https://product.beehiiv.com/…>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

Message

Content-Type: multipart/alternative; boundary="dmCfsIc+S72RLgZsPnF6cg"
From: "Tyler from beehiiv" <[email protected]>
Reply-To: "Tyler from beehiiv" <[email protected]>
Subject: message delivered
sId: a8e88f38-1bf6-4bad-8154-2c897fe51252
MIME-Version: 1.0
Date: Wed, 11 Nov 2026 14:06:39 +0000
Message-ID: <20261111.140639.a55efba6@mta18>

Similar campaigns from other brands

Different brands running the same play. Compare any of them side by side.

Morning Brew

☕ The in(box) crowd

Wed, Sep 2 · 9:01am ET

Compare

Archived for reference and commentary. Beehiiv, its logos and content are the property of their respective owners; Inbox Archive claims no affiliation and has disabled all links. If you own this content and would like it removed, get in touch.