> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/sending-subdomain-setup-and-troubleshooting/troubleshooting-email-authentication-issues.md).

# Troubleshooting Email Authentication Issues

A variety of tools exist to help you check if your emails are correctly authenticated.

## Send a Test Email

Send a test email from your subdomain and then **check the email headers**.

Most mailbox providers will indicate whether your email is correctly authenticated. For example, in Gmail, open the email, click the **three dots** in the top right corner, and select "**Show Original.**"

<figure><img src="/files/B4wmAm0Xx1AfbPfGHQIC" alt=""><figcaption></figcaption></figure>

## Use a DNS Debug Tool

You can also use dedicated DNS debug tools like [EmailStruff's DNS tool](https://emailstuff.org/dns).

#### → SPF:

* **Strict alignment**: Type your subdomain name in the TXT field of the tool (`subdomain.domain.com`)
* **Relaxed** **alignment**: Type your bounce subdomain name in the TXT field of the tool (`bounce.subdomain.domain.com`)

#### → DKIM

Type the selector + your subdomain name in the TXT field of the tool (`scphxxxx._domainkey.subdomain.domain.fr`).

#### → DMARC

Type `_dmarc.subdomain.domain.com` in the TXT field of the tool to check your DMARC record.

## Dig Command

Alternatively, you can use the `dig` command following the same logic:

```
dig TXT subdomain.domain.com
```

## Common Issues with Strict Alignment

When operating in strict alignment mode, the presence of **TXT entries** within the same domain **often disrupts email authentication**.

The most frequent cause is a **Google Postmaster Tools** verification code being incorrectly placed at the subdomain level. Ensure that you only verify your root domain with Google Postmaster Tools.&#x20;

Subsequent subdomains do not require individual verification to be added to the tool's monitoring.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/sending-subdomain-setup-and-troubleshooting/troubleshooting-email-authentication-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.