List-Unsubscribe Header Generator
Generate RFC-compliant unsubscribe headers for your email campaigns
Configuration
Usually "unsubscribe" or "optout"
Important: Your unsubscribe URL must include a subscriber-specific token (uid, hash, etc.) — a generic URL means all clicks unsubscribe the same person.
Generated Code
What is the List-Unsubscribe header and why does it matter?
The List-Unsubscribe header (RFC 2369) tells email clients how users can unsubscribe from your mailing list. It's required by GDPR, CAN-SPAM, and the new Google/Yahoo 2024 bulk sender requirements. Without it, your emails may be marked as spam or rejected entirely.
What are Google and Yahoo's 2024 bulk sender requirements?
Both Gmail and Yahoo now require one-click unsubscribe (RFC 8058) for bulk senders with >5,000 daily emails. You must include either a List-Unsubscribe-Post header (one-click) or an HTTPS URL that unsubscribes without requiring authentication. SPF, DKIM, and DMARC alignment is also mandatory.
What's the difference between RFC 2369 and RFC 8058?
RFC 2369 defines the List-Unsubscribe header (mailto and/or HTTP methods). RFC 8058 extends it with one-click unsubscribe (List-Unsubscribe-Post), which Gmail and Yahoo now prefer. RFC 8058 is more secure because it doesn't require users to click through to a webpage.
My ESP already handles unsubscribes — do I still need these headers?
Most ESPs add List-Unsubscribe headers automatically, but it's worth verifying. Check your email headers using tools like Google Toolbox for Gmail or a raw email viewer. If your ESP doesn't include them, you can add custom headers — this generator provides the exact code to use.
Related Tools
Why We Built This Tool
Google and Yahoo's February 2024 bulk sender requirement mandates List-Unsubscribe headers for senders above 5,000/day. Manual header construction is error-prone — incorrect formatting, missing one-click parameters, or broken endpoints cause ISP penalties. This tool generates tested, compliant headers for every language and framework.
What Goes Wrong Without This
Broken unsubscribe headers trigger ISP deferral and prevent compliance with Google/Yahoo requirements. Teams send headers in wrong format, forget one-click markers, or publish non-working endpoints. ISPs block or defer entire campaigns due to header misconfiguration.
Who This Tool Is For
E-commerce & DTC Brands
Generate compliant unsubscribe headers for campaign email. Test with Gmail and Yahoo to ensure one-click unsubscribe appears in the unsubscribe button.
Email Marketing Agencies
Provide code snippets for client ESPs and email builders. Ensure client campaigns send headers in the correct format — broken headers trigger ISP penalties.
B2B SaaS & Outbound Teams
Add List-Unsubscribe headers to transactional and cold email. Comply with Google/Yahoo requirements and avoid deferral from major ISPs.
Frequently Asked Questions
Why is List-Unsubscribe required?
What's the difference between List-Unsubscribe and List-Unsubscribe-Post?
Do I need both mailto and HTTPS methods?
Do I need an InboxEagle account to use this tool?
Compliance Headers Set — Now Monitor Your Sender Reputation
List-Unsubscribe headers protect your deliverability — but you also need clean SPF, DKIM, DMARC, and no blacklist listings. InboxEagle monitors all of that continuously.
Start Free 14-Day TrialNo credit card required · Cancel anytime