# Hostinger

> Publish the SPF, DKIM, and DMARC records MailBlastr generates for your domain using Hostinger’s DNS / Nameservers manager.

This guide walks through adding the DNS records MailBlastr generates for a domain using **Hostinger**. 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.

## Log in to Hostinger

1. **Open Domains** — Log in at auth.hostinger.com, select the **Domains** tab, and choose your domain from the **Domain portfolio** list.
2. **Open DNS / Nameservers** — Select **DNS / Nameservers** to reach the page where you manage DNS records.
3. **Add each record** — Use **Add Record** for every entry below — the DKIM TXT record, the SPF MX and TXT, and the DMARC TXT.

> **Warning:** Hostinger’s **Name** field expects only the subdomain part — enter `mailblastr._domainkey`, `send`, and `_dmarc`, never the full `…example.com`. Hostinger appends your domain automatically.

## DKIM — TXT

Add **one** TXT record holding your domain’s DKIM public key. Copy the value from your domain configuration page in MailBlastr.

**DKIM — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | A single DKIM key record. |
| `Name` | mailblastr._domainkey | No | Hostinger appends `.example.com`, giving `mailblastr._domainkey.example.com`. `mailblastr` is the fixed selector MailBlastr uses. |
| `Target` | v=DKIM1; k=rsa; p=<public key> | No | The DKIM key record holding your domain’s public key. |
| `TTL` | 3600 | No | Hostinger value used in these examples. |

## SPF — MX on the send subdomain

MailBlastr uses the custom MAIL FROM subdomain `send.example.com`. Set **Type** to `MX`, **Name** to `send`, paste the MailBlastr MX value into **Mail Server**, and set **Priority** to `10`.

**SPF — MX**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | MX | No | Receives bounce and complaint feedback for the MAIL FROM subdomain. |
| `Name` | send | No | Resolves to `send.example.com`. |
| `Mail Server` | feedback-smtp.us-east-1.amazonses.com | No | Region-specific feedback host. Replace `us-east-1` with your domain’s region. |
| `Priority` | 10 | No | Use `20`/`30` if `10` is already taken on that host. |
| `TTL` | 3600 | No | Hostinger value used in these examples. |

## SPF — TXT on the send subdomain

**SPF — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | SPF policy for the MAIL FROM subdomain. |
| `Name` | send | No | Same host as the MX — resolves to `send.example.com`. |
| `TXT value` | v=spf1 include:amazonses.com ~all | No | Authorizes Amazon SES for the MAIL FROM subdomain. |
| `TTL` | 3600 | No | Hostinger value used in these examples. |

## DMARC — TXT on _dmarc

**DMARC — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | DMARC policy record. |
| `Name` | _dmarc | No | Resolves to `_dmarc.example.com`. |
| `TXT value` | v=DMARC1; p=none; | No | A monitoring policy to start with. See [Implementing DMARC](https://www.mailblastr.com/docs/kb/dmarc). |
| `TTL` | 3600 | No | Hostinger value used in these examples. |

> **Note:** Hostinger gotchas: enter only the bare **Name** prefix (`send`, `_dmarc`, `mailblastr._domainkey`), never the full domain; and never reuse an existing MX priority on the same host.

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).