Free deliverability setup checker
Checks your complete technical setup
Checks spam blacklists
100% free
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Contrary to what most people believe…
High email deliverability doesn’t start with your subject line.
Instead, the foundation of getting your emails read is your technical setup.
The technical setup consists of your email authentication records and custom tracking domain.
We’ve created a tool that checks if your technical setup is in order.
It’s fast, accurate, and as a bonus, it also checks if your domain is on an email blacklist.
High email deliverability doesn’t start with your subject line.
Instead, the foundation of getting your emails read is your technical setup.
The technical setup consists of your email authentication records and custom tracking domain.
We’ve created a tool that checks if your technical setup is in order.
It’s fast, accurate, and as a bonus, it also checks if your domain is on an email blacklist.
How to use the deliverability setup checker
Just add your domain to the Your domain name field (1) and click Check domain setup (2)…
For these results, the email authentication and MX records are in order. However, the domain is on a blacklist, which would need to be addressed.
Your technical setup explained 👨🏻🏫
The technical setup is the machinery behind your email deliverability.
If it’s not functioning properly, many of your emails will land in the spam folder.
To help you understand better what it is and what it does, here’s a short explanation of each element of your technical setup:
➡️ SPF: Sender Policy Framework is an email authentication protocol. You implement it through a DNS record in which you specify which servers can send email through your domain. If you use an email service provider, you’d typically include their server in your SPF record. Receiving email servers can check the SPF record to verify that incoming emails are sent from an authorized server. If an email indeed comes from an unauthorized server, the receiving server may mark the email as spam or reject it entirely, helping to prevent spoofing and phishing attacks.
➡️ DKIM: DomainKeys Identified Mail authenticates the content of your email. It allows the receiving server to check if an email has been tampered with during transit. If it has, the email will fail authentication, potentially resulting in the email server rejecting the email or sending it to the spam folder.
➡️ DMARC: Although receiving servers have their own policies on what to do with unauthorized emails, Domain-based Message Authentication, Reporting and Conformance allows you to set yours. Your DMARC policy comes into play when an email fails SPF or DKIM authentication. You can either reject the email altogether, send it to spam, or let it pass regularly.
➡️ MX records: MX records tell sending servers where to send email. More specifically, to what receiving email servers should they send the email? If you don’t have MX records set up for your domain, sending servers won’t know where to send your incoming email. In other words, you won’t be able to receive email.
➡️ Custom Tracking Domain: To track clicks, opens, and other engagement metrics, your email-sending tool adds a tracking domain to your emails. Unfortunately, many of their customers, including spammers, use this tracking domain, lowering your deliverability. By using a Custom Tracking Domain, you’ll have better inbox placement.
If it’s not functioning properly, many of your emails will land in the spam folder.
To help you understand better what it is and what it does, here’s a short explanation of each element of your technical setup:
➡️ SPF: Sender Policy Framework is an email authentication protocol. You implement it through a DNS record in which you specify which servers can send email through your domain. If you use an email service provider, you’d typically include their server in your SPF record. Receiving email servers can check the SPF record to verify that incoming emails are sent from an authorized server. If an email indeed comes from an unauthorized server, the receiving server may mark the email as spam or reject it entirely, helping to prevent spoofing and phishing attacks.
➡️ DKIM: DomainKeys Identified Mail authenticates the content of your email. It allows the receiving server to check if an email has been tampered with during transit. If it has, the email will fail authentication, potentially resulting in the email server rejecting the email or sending it to the spam folder.
➡️ DMARC: Although receiving servers have their own policies on what to do with unauthorized emails, Domain-based Message Authentication, Reporting and Conformance allows you to set yours. Your DMARC policy comes into play when an email fails SPF or DKIM authentication. You can either reject the email altogether, send it to spam, or let it pass regularly.
➡️ MX records: MX records tell sending servers where to send email. More specifically, to what receiving email servers should they send the email? If you don’t have MX records set up for your domain, sending servers won’t know where to send your incoming email. In other words, you won’t be able to receive email.
➡️ Custom Tracking Domain: To track clicks, opens, and other engagement metrics, your email-sending tool adds a tracking domain to your emails. Unfortunately, many of their customers, including spammers, use this tracking domain, lowering your deliverability. By using a Custom Tracking Domain, you’ll have better inbox placement.
Deliverability setup checker FAQ
Can I use the deliverability checker on multiple domains?
You can use it as many times as you need.
What happens if my technical setup has issues?
Yes, you can use it on multiple domains.
Do you have generators for other email authentication protocols?
Your deliverability will tank. If your emails are not delivered properly, few people will read them. Your return on investment will suffer. Email outreach success starts with good deliverability.
How do I set up email authentication records like SPF, DKIM, and DMARC?
We have published guides to help you:
➡️ How to create an SPF record
➡️ How to set up DKIM for your domain
➡️ How to set up DMARC
How do I set up my domain’s MX records?
We’ve got you covered too. Here’s how to set up your MX records.
Can I use the deliverability checker on multiple domains?
You can use it as many times as you need.
What happens if my technical setup has issues?
Yes, you can use it on multiple domains.
Do you have generators for other email authentication protocols?
Your deliverability will tank. If your emails are not delivered properly, few people will read them. Your return on investment will suffer. Email outreach success starts with good deliverability.
How do I set up email authentication records like SPF, DKIM, and DMARC?
We have published guides to help you:
➡️ How to create an SPF record
➡️ How to set up DKIM for your domain
➡️ How to set up DMARC
How do I set up my domain’s MX records?
We’ve got you covered too. Here’s how to set up your MX records.
Frequently Asked Questions
Sign-up for free
How many times can I use the SPF generator?
You can use it as many times as you need.
Can I add multiple providers to my SPF record?
Yes, just click all the email service providers you send email with.
Do you have generators for other email authentication protocols?
Yes, we have a DMARC generator too.
What happens to an email if it fails SPF authentication?
You can decide what happens to them by setting up a valid DMARC record. Receiving servers will typically follow the policy you set in your DMARC record. DMARC's three main policies are None (email gets a pass), Quarantine (email gets sent to spam), and Reject (email won't get delivered at all).
What happens if I send from a service not included in my SPF record?
Your emails will fail authentication and likely get sent to spam or not get delivered at all.