Understanding Email Deliverability Standards
Email deliverability is the measure of how successfully sent messages reach the recipient's inbox rather than being filtered, delayed, or routed to the spam folder. Modern email receivers, such as Gmail and Yahoo, enforce strict standards to protect users from spam, phishing, and unwanted bulk mail.
To help domain owners, operations personnel, and sending teams prepare their mail streams, the Email Deliverability Checklist provides a structured review of domain authentication, infrastructure, and sending practices. The tool evaluates the domain, context, and completed steps entered by the user against a static reference set dated 2026-07-16. This reference set summarizes published standards and provider guidance from that date.
Using a checklist helps identify gaps in your configuration before you send transactional, bulk, or subscribed mail. However, completing every item does not guarantee inbox placement. Receivers also evaluate real-time reputation, recipient feedback, message content, traffic patterns, and changing internal rules.
Domain Authentication: SPF, DKIM, and DMARC
Domain authentication proves to receiving servers that an email actually originated from the domain listed in the visible From header. Proper authentication is the foundation of email deliverability.
- SPF (Sender Policy Framework): This standard allows domain owners to publish a list of IP addresses or subservices authorized to send mail on behalf of their domain. A key requirement is ensuring that your SPF covers every sending service. This means verifying the domain has one SPF policy and it includes every provider or IP allowed to send.
- DKIM (DomainKeys Identified Mail): This protocol adds a cryptographic signature to email headers, verifying that the message was sent by the domain owner and has not been altered in transit. You must ensure DKIM signing is active with a suitable key. This involves inspecting a delivered message for DKIM=pass and confirming the signing key is at least 1024 bits, though 2048 bits should be used when supported.
- DMARC (Domain-based Message Authentication, Reporting, and Conformance): DMARC ties SPF and DKIM together. It requires that DMARC is published with at least p=none. To verify this, look up _dmarc on the From domain and validate the record before moving gradually to quarantine or reject.
- Alignment: Authentication is only effective if SPF or DKIM aligns with the visible From domain. You must check Authentication-Results on a real message and confirm at least one passing authenticated domain aligns with the From domain.
If basic authentication is missing, the tool highlights the required current requirement: Set up SPF or DKIM. This requires you to publish a complete SPF policy or enable DKIM signing, then send a real message and confirm the chosen method passes.
Infrastructure and Message Formatting
Properly configured infrastructure and valid message headers prevent receiving servers from flagging your mail as suspicious.
| Infrastructure Element | Verification Step |
|---|---|
| Forward and reverse DNS | Confirm that forward and reverse DNS agree for sending IPs. Each sending IP must have a PTR hostname, and that hostname must resolve back to the same IP. |
| TLS Encryption | Ensure outbound mail uses TLS. Check your sending service or SMTP logs to confirm supported receivers are offered an encrypted TLS connection. |
| Headers and Identity | Verify headers and sender identity are valid and accurate. Inspect a real message for one From address, valid Date and Message-ID fields, and a subject and identity that are not misleading. |
Sending Practices and List Management
Maintaining a healthy sender reputation requires strict list hygiene and explicit recipient consent.
- Consent and List Hygiene: Ensure recipients opted in and invalid addresses are removed. Review signup evidence, suppress hard bounces and complaints, and stop mailing recipients who no longer want the stream.
- Complaint Monitoring: Ensure complaint rates are monitored below published thresholds. Review provider dashboards regularly; keep Gmail spam rates below 0.10% and avoid 0.30% or higher, and keep Yahoo complaints below 0.30%.
- Feedback Loops: Ensure authentication, reputation, bounces and reports are reviewed. Use DMARC aggregate reports and available provider dashboards or feedback loops to investigate failures and remove bad sources.
Unsubscribe Mechanisms
For marketing or subscribed mail, providing a clear and functional unsubscribe mechanism is mandatory under modern provider guidelines.
- One-Click Unsubscribe Headers: Ensure one-click unsubscribe headers work. Send a subscribed message with RFC 8058 List-Unsubscribe and List-Unsubscribe-Post headers, then test the HTTPS POST endpoint.
- Visible Unsubscribe: Ensure a visible unsubscribe works and requests are handled promptly. Test the body link without signing in and confirm suppression completes within two days.
Using the Tool and Privacy
To use the tool, enter your sending domain in the Sending domain field. The domain must be a valid public domain, such as mail.example.com, and must be within 253 characters. You can toggle the Bulk sender switch if you send approximately 5,000 or more messages a day to personal Gmail accounts, or if your provider treats the stream as bulk mail. Toggle Marketing or subscribed mail for newsletters, promotions, and other subscribed messages.
Mark the checklist items you have already completed, then click Generate review steps. The tool will output a Sender review showing the status of your domain.
If the domain input is empty when generating a review, the tool displays:
Enter the sending domain first.
If the domain is longer than 253 characters, it displays:
That domain is unusually long. Keep it within 253 characters.
If the domain is invalid, it displays:
Enter a public domain only, such as mail.example.com.
When you click Clear, the domain input is emptied, results are cleared, and the status Checklist cleared. is displayed. When all applicable items are checked, the tool displays:
No unchecked items in this reference set and Keep monitoring real messages, reports and provider guidance because status and requirements can change.
Your domain and checklist selections stay in your browser; BroBroGo does not upload or save them. The work happens on the user's device, and no data leaves the device.
FAQ
Which rules does this checklist use?
The 2026-07-16 reference set uses RFC 7208 for SPF, RFC 6376 for DKIM, RFC 9989 for DMARC, RFC 8058 for one-click unsubscribe, and the Gmail and Yahoo sender guidance available on that date.
Does the checklist query DNS or send a test email?
No. It evaluates only the domain, context and boxes you enter. Follow the generated steps with your DNS provider, sending service and real message headers.
Does completing every item guarantee inbox placement?
No. Receivers also use reputation, recipient feedback, content, traffic patterns and changing internal rules. This checklist helps prepare a review; it cannot predict or promise delivery.