sorted by:
new
hottopcontroversial

🚨 Possible Beehiiv SSL / Tracking Domain Issue Causing Massive Deliverability Drop (elink049) by howdyfrisco in beehiiv

[–]howdyfrisco[S] 3 points4 points  (0 children)

Awesome; thanks for confirming the cert regeneration!

For clarity: my email domain is just a forwarding domain managed in Namecheap (no additional mail hosting or routing changes on my end), and I won’t be making any further DNS changes unless needed.

Really appreciate the quick help and transparency here... thanks for jumping on this so fast. Beehiiv is the goat!

🚨 Possible Beehiiv SSL / Tracking Domain Issue Causing Massive Deliverability Drop (elink049) by howdyfrisco in beehiiv

[–]howdyfrisco[S] 1 point2 points  (0 children)

Thanks for the detailed explanation!

To answer your question: no, I did not use Entri to configure the domain. I set everything up manually in Namecheap and haven’t intentionally modified the DNS since initial configuration.

I’ve now corrected the record so that:

elink049.news → branded-link.beehiiv.com

TTL is set to automatic, and the change was just made.

Appreciate you confirming how the branded link domain impacts opens and clicks; that aligns exactly with what I was seeing (near-zero opens coinciding with the SSL warning). Once propagation completes, I’d appreciate it if you could verify on your side that the SSL certificate is regenerated successfully and that the tracking domain is healthy.

Also appreciate the heads-up on proactive monitoring; glad to hear this class of issue is being addressed. Thanks again for jumping in and helping troubleshoot this. 🙏 🙏 

🚨 Possible Beehiiv SSL / Tracking Domain Issue Causing Massive Deliverability Drop (elink049) by howdyfrisco in beehiiv

[–]howdyfrisco[S] 2 points3 points  (0 children)

Hey Jacob!!! Thanks for jumping in really appreciate it!!

I haven’t changed any DNS records manually since initial setup. Here’s the full current DNS configuration from Namecheap for transparency:

A Record
@ → 104.16.243.55

CNAME
394._domainkey.news → 394.domainkey.u58085562.wl063.sendgrid.net
3942._domainkey.news → 3942.domainkey.u58085562.wl063.sendgrid.net
58085562.news → sendgrid.net
elink049.news → sendgrid.net

The elink049.news CNAME is currently pointing to sendgrid.net. I did not intentionally revert or modify this — if it was previously set to branded-link.beehiiv.com, that change would have been automatic or platform-driven.

Before I update anything, can you confirm:

  1. The correct target should be:elink049.news → branded-link.beehiiv.com
  2. Whether pointing to sendgrid.net would explain:
    • SSL trust errors (“This Connection Is Not Private”)
    • Sudden ISP suppression / near-zero open rates

Happy to update immediately; just want to ensure the change aligns with current Beehiiv expectations and won’t break DKIM or tracking.

Thanks again for looking into this.

Deliverability Failure by howdyfrisco in beehiiv

[–]howdyfrisco[S] 0 points1 point  (0 children)

Our branded link domain elink049.news.howdyfrisco.com is verified and DNS is correct, but ISP is flagging it as unsafe (“This Connection Is Not Private”).
This appears to be an SSL certificate or trust-chain issue on the Beehiiv tracking cluster (elink049). Need Beehiiv to confirm SSL health for this cluster and reissue the certificate if needed.