# Strato

> Publish the SPF, DKIM, and DMARC records MailBlastr generates for your domain on Strato — including creating the send subdomain to host the MX record.

This guide walks through adding the DNS records MailBlastr generates for a domain using **Strato**. Add your domain in MailBlastr first to generate the records — see [Managing domains](https://www.mailblastr.com/docs/domains/managing) — and keep the [DNS records](https://www.mailblastr.com/docs/domains/dns) reference open for your exact DKIM record and region.

It is best practice to use a [subdomain](https://www.mailblastr.com/docs/kb/subdomain-vs-root) (e.g. `updates.example.com`) instead of the root domain for reputation segmentation.

> **Warning:** By default Strato domains use the Strato mail server (the `mail` send path). To host MailBlastr’s MAIL FROM MX you must **create a `send` subdomain** and set the MX record there, bypassing the default.

## Log in to Strato

1. **Open Domain Manager** — Log in to your Strato account and, in the left-hand navigation, go to **Domains → Manage Domain**.
2. **Open settings** — Click the **gear icon** on the domain to open its Settings, where the DNS records live.
3. **Add each record** — Add every entry below — the DKIM TXT record, the SPF MX (on a `send` subdomain) and TXT, and the DMARC TXT.

## DKIM — TXT

On the base domain’s **DNS** tab, manage the TXT records and add **one** TXT record holding your domain’s DKIM public key. DKIM values are **case-sensitive** and must match exactly; copy the value with the copy icon in MailBlastr.

**DKIM — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | A single DKIM key record. |
| `Name` | mailblastr._domainkey | No | Resolves to `mailblastr._domainkey.example.com`. `mailblastr` is the fixed selector MailBlastr uses. |
| `Value` | v=DKIM1; k=rsa; p=<public key> | No | The DKIM key record holding your domain’s public key. Must match exactly — DKIM is case-sensitive. |

## SPF — MX on the send subdomain

Create a new subdomain named `send`, open its settings, go to the **DNS** tab, and **manage** its MX record. Select **own mail server**, paste the MailBlastr MX value into the **Server** field, and use the default priority **Low**.

**SPF — MX**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | MX | No | Receives bounce and complaint feedback for the MAIL FROM subdomain. |
| `Name` | send | No | The `send.example.com` subdomain you created. |
| `Mail server` | feedback-smtp.us-east-1.amazonses.com. | No | Region-specific feedback host (keep the trailing dot). Replace `us-east-1` with your domain’s region. |
| `Priority` | Low | No | Strato’s default priority setting for an own mail server. |

## SPF — TXT on the send subdomain

On the base domain settings, go to the **DNS** tab, manage TXT/CNAME records, and click **Create another record**. Choose **TXT**, set **Name** to `send`, and enter the SPF value.

**SPF — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | SPF policy for the MAIL FROM subdomain. |
| `Name` | send | No | Resolves to `send.example.com`. |
| `Value` | v=spf1 include:amazonses.com ~all | No | Authorizes Amazon SES for the MAIL FROM subdomain. |

## DMARC — TXT on _dmarc

Strato may provide a standard DMARC record (e.g. `v=DMARC1; p=reject;`). MailBlastr recommends starting at `p=none;` to monitor first, then tightening — see [Implementing DMARC](https://www.mailblastr.com/docs/kb/dmarc).

**DMARC — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | DMARC policy record. |
| `Name` | _dmarc | No | Resolves to `_dmarc.example.com`. |
| `Value` | v=DMARC1; p=none; | No | A monitoring policy to start with; tighten to `quarantine` or `reject` later. |

> **Note:** Strato gotchas: you **must** create the `send` subdomain to host the MAIL FROM MX (the default `mail` path won’t work); DKIM values are **case-sensitive** — copy them exactly; and keep the trailing dot on the MX value.

Once all six records are saved, return to MailBlastr and [re-verify the domain](https://www.mailblastr.com/docs/api/domains-verify). If it stays pending, see [What if my domain isn’t verifying?](https://www.mailblastr.com/docs/kb/domain-not-verifying).