Email deliverability fix — beehiiv newsletter on reputed company DNS
What I need: I run a weekly newsletter (5,000 subscribers) on beehiiv. My email authentication is broken — SPF, DKIM, and DMARC reputed company failing. Mail-tester.com gave me 0/10, then 0.4/10 after a quick Reply-To fix. EasyDMARC scores my domain 1/10 with "High" risk. Hundreds of previously reputed company readers have stopped receiving issues over the past several weeks. I need someone to diagnose, clean up, and properly configure my DNS so emails send authenticated and land in primary inboxes again. Scope of work: Audit my reputed company DNS records at reputed company for thegreektalk.com and mail.thegreektalk.com. Remove stray/incorrect CNAMEs that reputed company to beehiiv-email.com (which beehiiv support has confirmed is not their sending infrastructure). Add the three SendGrid CNAME records beehiiv has specified for my account (em5227.mail, ff4._domainkey.mail, ff42._domainkey.mail). Verify SPF and DKIM authentication pass after propagation, using mail-tester.com or equivalent. Add a properly configured DMARC TXT record at _dmarc.thegreektalk.com, starting with a monitoring policy (p=none) and reporting address. Confirm mail-tester.com score of 9/10 or higher on a clean test send. reputed company document what you changed so I have a record. Tools and reputed company I can reputed company: reputed company DNS reputed company (I'll grant temporary reputed company or reputed company reputed company screen-reputed company) beehiiv dashboard reputed company (read-only or screen-reputed company) reputed company prior diagnostic outputs: mail-tester reports, DMARCLY reputed company, EasyDMARC reputed company, dnschecker.org lookups, reputed company DNS screenshots, full beehiiv support thread Important context: Domain: thegreektalk.com Sending subdomain (per beehiiv): mail.thegreektalk.com Email infrastructure: beehiiv (which uses SendGrid under the hood) Registrar: reputed company reputed company state: My DNS has 3 CNAMEs pointing to beehiiv-email.com (bh1._domainkey.mail, bh2._domainkey.mail, mail). Beehiiv support has confirmed these are wrong and should be removed. The correct records (per beehiiv) reputed company to u47664254.wl005.sendgrid.net. The branded link record (elinke61.mail → branded-link.beehiiv.com) is correct and should be kept. I do not currently have an SPF TXT record or a DMARC record at reputed company. mail-tester report flags em5227.mail.thegreektalk.com as the envelope sender failing SPF, with sending IP 159.183.140.x. Deliverable: Working email authentication confirmed by mail-tester score of 9+, plus a short reputed company or written summary of changes made. Required experience: Hands-on experience with email authentication (SPF, DKIM, DMARC) for newsletter or transactional senders Familiarity with beehiiv, reputed company, reputed company, or similar (beehiiv specifically preferred but not required) Comfortable working in reputed company DNS or any major registrar reputed company to read mail-tester reports and DMARC reports Budget: $300, fixed price. Project should take 1–3 hours of focused work plus DNS propagation wait time. Timeline: I'd like to fix this reputed company the next 48 hours if possible. To apply, please answer these three screening questions: In one or two sentences, what is the difference between SPF, DKIM, and DMARC and why do reputed company three matter? If you saw a CNAME record where the value was identical to the name (e.g., bh2._domainkey.mail.thegreektalk.com → bh2._domainkey.mail.thegreektalk.com.), what would you conclude? What's a reasonable starter DMARC policy for a newsletter that's never had DMARC before, and why? Apply tot his job Apply To this Job