... During August I found that emails with my own email domain got into the spam folder in Gmail no matter how I made a delivery. SPF, DKIM and DMARC verification passed smoothly and the domain was not on any blocklist. I tested four kinds of sending a message with 'test' only and no links: first from my Workspace, then SocketLabs, an old hosting email server, and finally via Gmail API. All four resulted in spam. Consequently, I believed the issue ...

... answer was a generic checklist, because ChatGPT can't read your DNS. This week, mailX went live inside ChatGPT , as a plugin approved by OpenAI. Ask the question with your domain, and ChatGPT runs a live check through mailX: SPF, DKIM, DMARC and BIMI, with the exact record found Your DKIM selector, detected for you (we test 25 common ones) Blacklists: Spamhaus, Barracuda, SpamCop and more The fixes, in priority order SPF

... What the report shows A score out of 100. The same email always gets the same score, so you can re-test after each fix and see exactly what changed Placement estimates for Gmail, Outlook, Yahoo and Apple Mail SPF, DKIM and DMARC results, including alignment with your From domain Your sending IP and domain checked against major blacklists Your DNS setup: MX, PTR, MTA-STS, TLS-RPT, BIMI A SpamAssassin score with every rule that fired Every fix, ranked ... ... Comment from Chantal Ross(@chantal_r): I found this thread just in time as my launch is just a few days away! I'll be sure to check it out Comment from Saman Baloch(@saman_baloch): For me, checking SPF

... Saqib, a freelance email deliverability specialist. Tomorrow I'm launching OutboundAuth ( outboundauth.com ) here on Product Hunt a free toolkit I built from my day-to-day client work: SPF, DKIM & DMARC audits in plain language (no jargon) SPF

... were on Google Workspace with a custom domain. Our onboarding emails, trial expiry warnings, and password resets were landing in spam for nearly 40% of them. Root cause: we had switched sending providers in December and never set up SPF, DKIM, and DMARC records for the new provider. We had been sending authenticated mail through the old provider and unauthenticated mail through the new one for 10 weeks. Fix took 3 days: DNS records, a subdomain dedicated to transactional mail ...

... that VegaMailer is officially live! VegaMailer is an email marketing platform built for creators, marketers, and SaaS founders who need reliable deliverability and flexibility without complex overhead. What makes VegaMailer stand out: High Deliverability: Clean API engine with automated SPF, DKIM, and DMARC domain verification. BYO-SMTP Flexibility: Connect your own SMTP keys (SendGrid, Mailgun, Brevo, etc.) for complete volume control. Smart Security & Compliance: Built-in 2FA (TOTP) security and automated webhook suppression to protect sender reputation. Special Offer ...

... newsletter from used to open at 50 to 61%. I went quiet for about a year, came back, and fired off promotional subject lines two and three in a row. December was 33.7%. By May it was 9.6%. SPF, DKIM and DMARC passed the entire time. What was burnt was reputation on that domain and that local part, not authentication, so there was nothing in DNS to fix. Fixing it meant manufacturing engagement. One route only, nothing mixed in. Start ...

... Over the last few weeks I noticed that most email tools were scattered across different websites. You'd use one site for SPF, another for DKIM, another for MX lookup, and another for temporary email. So I decided to build @FreeMailTools a growing collection of free email utilities in one place. Current features include: Email Validator Temporary Email MX Lookup SPF

... service. Your inbox, now with a healthy sense of suspicion. New Phishing detection, built right in. Skim now quietly vets every message for the classic tells and warns you before you click something you'll regret. Sender checks reads SPF / DKIM / DMARC results, catches "reply goes to a totally different domain" tricks, spots when the friendly display name hides a stranger's address, and flags lookalike domains ( paypa1.com , we see you). Link checks a link that says one thing ...

... built for security teams and read like RFCs, so I built  HealthCheck Email ( healthcheckemail.com ) for marketers and founders instead: Enter a domain and get an  A+ to F email health grade  in seconds, covering DMARC, SPF, DKIM, MX, blacklists, and TLS It parses the reports mailbox providers send about your domain, so you see  every service actually sending as you , with names like Google Workspace and Klaviyo instead of IP addresses A guided path from DMARC ...

... Product Hunt I'm Rodrigue, solo founder from Kigali, Rwanda. I built Infraova after seeing the same problem repeat itself: people running email campaigns have zero visibility into what's happening to their domain after setup. SPF breaks silently after adding a new tool. Domains get blacklisted with no alert. Someone starts spoofing your domain and sends emails pretending to be you. SSL expires. DNS records change without warning. You find out when a campaign fails or a client calls ... ... then the damage is done. Infraova monitors your domain 24/7 across 25 checks SPF

... filtered by default a sharper native Mac inbox, with better bulk actions, label editing, spam recovery, attachment actions, and composing stronger privacy defaults, including proxied remote images and opt-in read receipts a free email domain checker for MX, SPF, DKIM, DMARC, reverse DNS, and blocklists We wrote up the full changelog here: https://bangermail.com/blog/what... What would make your native Mac email app feel meaningfully better? Comment from Zajin Dacos(@zajindacos123_coder): the privacy updates are interesting ...

... support ticket automatically receives its own unique, cryptographic routing address ( record_id-org_id@yourdomain.com ). Outbound and inbound threads permanently lock to that specific record's vertical timeline. Full BYOD Domain Freedom: Connect your business domain in seconds with full native support for SPF, DKIM, and DMARC verification to aggressively protect your sender reputation while scaling outreach. Extension-Free Google Sync: If you live in Gmail, you don t have to leave it. Our bidirectional OAuth integration mirrors your communications in real-time server ...

... video conferencing inside the inbox. We're relaunching on Product Hunt soon with a lot of new features, and before we do, I wanted to open the floor. We've spent the last year deep in email infrastructure SPF, DKIM, DMARC, bounce handling, deliverability tuning, bulk sending, cold outreach sequences, white-label hosting, IMAP/SMTP, the works. If you have questions about any of it, ask below. Happy to go as deep as needed. Cold email deliverability and domain health ... ... vs

... that analyze thousands of signals engagement history, sender reputation, authentication alignment, complaint rates. In February 2024 this got a lot more concrete. Google and Yahoo rolled out new requirements for senders pushing more than 5,000 emails per day: SPF, DKIM, and DMARC became mandatory, one-click unsubscribe was required, and spam complaint rates had to stay below 0.10% in Postmaster Tools. Cross 0.30% and your mail gets rejected outright. From November 2025, Gmail tightened enforcement further. That's what ... ... your emails? I recently audited an EdTech company in Los Angeles. They send regular informational emails to educators across the US. Nothing promotional. Purely informational. They've been in business for almost two decades. They did everything right: SPF

... Been wrestling with deliverability lately. Warmup, SPF/DKIM/DMARC, dedicated IPs vs shared, sending volume ramps. It's a deceptively deep rabbit hole. I'm curious what's actually working for people in 2026 versus

... still kept finding serious external security gaps. Not always one-click hack type issues, but the kind of problems that slowly stack up into real risk: - exposed admin/login surfaces - weak or missing security headers - bad TLS/configuration issues - missing SPF, DKIM, or DMARC records - forgotten staging/dev endpoints - open ports that should not be public - outdated services - sensitive files accidentally exposed - redirects and auth flows that were not properly hardened The pattern was clear: AI helps people ship faster, but it does ... ... that "looks fine from the outside" you're describing. The AI got me 90% there, and then the last 10%, the stuff that actually matters, was human review. Comment from Nate(@ndmventures): I built DMARCdrift to help with the SPF

... same gaps appeared repeatedly across stacks, including modern SaaS tools, AI products, and production web apps. Content Security Policy was absent. Frame protections were not enforced. MIME sniffing protections were missing. Referrer policies were not defined. Permissions were unrestricted. SPF and DMARC were not configured. These are baseline controls, not advanced hardening. Why This Matters A C to B range does not indicate a secure system. It indicates a partially configured one. Transport is protected, but execution and domain trust ... ... default. That distinction is where risk accumulates. DLX7 Positioning DLX7 is designed to expose this gap through externally observable signals and contextual analysis. It does not rely on assumptions or internal claims. It surfaces what is actually enforced versus