> For the complete documentation index, see [llms.txt](https://docs.hostinger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostinger.com/reach/sending-domain.md).

# Sending Domain

Connect and verify a sending domain in Hostinger Reach with SPF, DKIM, and DMARC records, and keep campaigns landing in the inbox rather than in spam.

Reach sends from your own domain, which means proving to receiving mail servers that you're allowed to. That's what the sending domain setup does. Until it's verified, campaigns can't go out.

Find it under **Settings** → **Domain**. Each [workspace](/reach/overview.md#workspaces) connects one sending domain at a time.

## The records

Three DNS records do the work, and Reach checks each one:

| Record    | What it does                                                                         |
| --------- | ------------------------------------------------------------------------------------ |
| **SPF**   | Lists Reach as allowed to send for your domain, so your mail isn't treated as forged |
| **DKIM**  | Signs each message cryptographically, letting receivers confirm it wasn't altered    |
| **DMARC** | Tells receivers what to do with mail that fails the checks above                     |

The page shows the exact values to use, since DKIM is unique per domain. Copy them from there rather than from anywhere else.

## Connecting

* **Domain registered at Hostinger** — Reach can add the records for you.
* **DNS hosted elsewhere** — copy each record into your DNS provider, then re-check. Propagation is usually quick but can take several hours.

Each record shows whether it passed, so a partial setup is easy to spot. A domain that isn't fully verified reports which record is still missing.

> **Note:** This is separate from the DNS setup for [mailboxes](/emails/domain-settings.md). A domain can send marketing mail through Reach and host mailboxes at the same time, but the records serve different purposes and both need to be right.

## Deliverability warnings

Reach watches how receivers treat your mail and warns you in the app when something's wrong. Warnings fall into two kinds:

* **Needs attention** — a lot of mail isn't arriving as expected. Sending still works, but it will be suspended if the pattern continues.
* **Sending blocked** — too much of your mail was treated as spam or generated complaints. Sending stops until the problem is reviewed.

Both name the affected domain. A blocked domain needs a review request through Customer Support, after you've addressed the underlying cause: the content, the list, or how the addresses were collected.

A sender mailbox or domain can also be suspended outright following high bounce rates, spam reports, or policy violations.

## Bounces and list hygiene

A bounce is a message the receiving server refused.

* **Hard bounce** — permanent. The address doesn't exist or rejects you outright.
* **Soft bounce** — temporary. A full mailbox, a rate limit, a server having a bad day.
* **Dropped** — rejected before delivery was attempted.

A campaign's **Recipients** tab breaks these out per contact with the reason given.

> **Note:** Hard-bounced contacts are **not** unsubscribed automatically. They stay subscribed and keep being mailed, which pushes your bounce rate up and your reputation down. Delete them periodically from the campaign's **Recipients** tab.

Reach also stops a large campaign mid-send if too much of the first batch is rejected, so one bad list doesn't damage your domain for everything that follows.

## Keeping deliverability healthy

* Send to people who asked for it — turn on [double opt-in](/reach/settings.md#subscribe-settings) if you collect addresses through [forms](/reach/forms.md).
* Never buy or scrape lists; they generate the complaints that get domains blocked.
* Clear hard bounces after each campaign.
* Make unsubscribing easy. An unsubscribe is far better for you than a spam complaint.
* Run the [quality checker](/reach/templates.md#quality-checker) before sending.

## Related pages

* [Campaigns](/reach/campaigns.md) — send failures caused by domain problems
* [Settings](/reach/settings.md#sender-details) — the name and address your mail comes from
* [Email Domain Settings](/emails/domain-settings.md) — the equivalent records for mailboxes

***

*Last updated: August 21, 2026*