So your emails land in the inbox.
When your emails disappear into spam, the right DNS records are usually missing. I set up SPF, DKIM and DMARC so your mail actually arrives.
← All servicesWhen email ends up in spam, it's rarely random. Modern mail providers — Gmail, Outlook, Apple Mail — run every incoming message through a set of authentication checks before deciding where to put it. Those checks look at three things: does the SPF record authorise the sending server, does the DKIM signature prove the message hasn't been tampered with, and what does DMARC say to do if either check fails? A missing or misconfigured record tips the balance toward the spam folder.
SPF (Sender Policy Framework) is a DNS TXT record that lists which servers are allowed to send on behalf of your domain. If you use a third-party tool like Mailchimp or HubSpot, that provider's servers need to be explicitly listed — otherwise the check fails. DKIM (DomainKeys Identified Mail) works differently: it adds a cryptographic signature to every outgoing message, which the recipient's server can verify using a public key published in your DNS. DMARC ties it all together, tells receiving servers what action to take when a message fails either check, and sends you aggregate reports so you can see what's happening.
Getting all three set up correctly — and aligned with each other — is where most inbox problems get solved. I check your current setup, find what's missing or broken, and fix it. That includes any third-party senders you use, so nothing falls through the cracks.
- SPF, DKIM and DMARC set up correctly
- No more emails landing in spam
- Analysis of why delivery is failing right now
- The right records for your mail provider
- DMARC reports set up in plain language
- A better reputation for your domain with mail providers
- Audit the current state: I check which records exist, whether SPF, DKIM and DMARC are present, and whether they're correctly aligned with each other.
- Create or fix the SPF record: I determine which servers are allowed to send for your domain and add all relevant providers — including any third-party tools.
- Activate DKIM keys at your mail provider and publish them as TXT records in DNS — separately for each sending service you use.
- Set a DMARC policy and configure reports, so you have ongoing visibility into what's being sent in your name and whether it's passing authentication.
- Businesses whose newsletters keep going to the spam folder
- Freelancers and agencies whose invoices get filtered before they're read
- Anyone using third-party senders like Mailchimp, Brevo or HubSpot
- Those who started experiencing delivery problems after switching hosts
- Anyone who needs to be confident that important emails actually arrive
Why do my emails land in spam?
Usually one of the three authentication records is missing: SPF, DKIM or DMARC. Without them, spam filters can't verify your mail and flag it as suspicious. A poor domain reputation or sending through an unauthorized server can also block delivery.
What are SPF, DKIM and DMARC?
SPF (Sender Policy Framework) is a DNS TXT record that specifies which servers are allowed to send email for your domain. DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing mail that recipients can verify. DMARC ties both together and tells receiving servers what to do with mail that fails — and sends you reports on it.
How do I improve email deliverability?
First I check whether SPF, DKIM and DMARC are correctly set up and aligned with each other. Then I confirm your mail provider is listed in the SPF record and that DKIM is active. After that I set a suitable DMARC policy and enable reports, so you can see what's working long term.
What does a DMARC report actually tell me?
DMARC reports show you daily which servers sent email in your name — and whether those emails passed the SPF and DKIM checks. That lets you quickly spot if someone is spoofing your domain, or if a legitimate sender still needs to be added to your SPF record.