# How do you add email DNS records in Hostinger?

URL: https://iblockspam.com/blog/add-email-dns-records-hostinger
Last updated: 2026-10-22
Published: 2026-10-22
Topic: Setup guides
Author: iBlockSpam Team

> How to add MX, SPF, DKIM and DMARC records in Hostinger hPanel, what goes in the Name field, how to replace Hostinger Email records, and how to check them.

## Short answer

In Hostinger hPanel, go to Domains, choose your domain and open DNS / Nameservers (or DNS). In Manage DNS records, pick the type (MX, TXT or CNAME), enter @ for the root or a prefix such as _dmarc, add the value and priority your provider gives, and select Add Record. Delete Hostinger Email records you no longer use.

Hostinger's hPanel puts every DNS record for a domain on one page, and new domains often come with Hostinger Email records already in place. Adding records is quick; the parts that cause trouble are leftover Hostinger MX and SPF records and the 4-hour default TTL.

This guide covers adding MX, SPF, DKIM and DMARC records in Hostinger, using Hostinger's own help articles for each step. Menu names are correct at the time of writing (October 2026), and Hostinger's articles currently show two slightly different paths, so both are given. If you need a refresher on the records themselves, read [SPF vs DKIM vs DMARC](https://iblockspam.com/blog/spf-vs-dkim-vs-dmarc).

## Does your domain use Hostinger's nameservers?

Hostinger's DNS zone only matters if your domain uses Hostinger's nameservers. Its DMARC article puts it plainly: "Records in Hostinger's DNS zone take effect only when your domain uses its assigned Hostinger nameservers" ([Hostinger](https://www.hostinger.com/support/8412851-how-to-add-a-dmarc-record-for-hostinger-email/)).

If the domain points to Cloudflare or another DNS host, make the changes there; our [Cloudflare guide](https://iblockspam.com/blog/add-dmarc-spf-dkim-records-cloudflare) covers that case. Our [MX Lookup](https://iblockspam.com/tools/mx-lookup) shows your domain's live nameservers. A domain registered elsewhere can still use Hostinger's DNS zone once it points to Hostinger's nameservers.

## Where do you add DNS records in Hostinger?

Hostinger's articles currently describe two routes to the same screen:

- **Newer path:** in the left sidebar, choose **Domains**, then **DNS**, and select your domain ([Hostinger](https://www.hostinger.com/support/1583249-how-to-manage-my-dns-records-on-hpanel)).
- **Older path:** go to **Domains**, select **Manage** next to the domain, then open **DNS / Nameservers** ([Hostinger](https://www.hostinger.com/support/4443666-how-to-manage-mx-records-in-hpanel)).

Then, in **Manage DNS records**:

1. Choose the record **Type**.
2. Fill in the fields below.
3. Select **Add Record**.

To change a record, edit or delete it in the list below the form. The fields:

| Field | Shown as | What to enter |
|---|---|---|
| **Type** | Type | MX, TXT or CNAME |
| **Name** | Name (Host) | `@` for the root domain, or only the prefix, such as `_dmarc`. Hostinger describes it as the hostname "without the domain name" ([Hostinger](https://www.hostinger.com/support/4738777-how-to-manage-cname-records-at-hostinger/)) |
| **Value** | TXT Value, Mail server (Points to), Target (Points to) | The value your provider gives you |
| **Priority** | Priority | MX only. Lower numbers are tried first |
| **TTL** | TTL | Hostinger's default is 14400 seconds (4 hours) |

Hostinger supports "A, CNAME, MX, TXT, AAAA, NS, SRV, and CAA" records ([Hostinger](https://www.hostinger.com/support/1583250-what-dns-record-types-are-supported-at-hostinger)). It also keeps a **DNS history** tab with a **Restore** option, and an export that downloads a BIND-format zone file. Export before you change anything.

### Why the 4-hour TTL matters

The TTL (time to live) tells resolvers how long to cache a record. With 14400 seconds, a mistaken MX record can stay cached for up to four hours after you fix it. Before an MX move, lower the TTL on the current MX records to around 300 seconds a day ahead. Our [DNS TTL guide](https://iblockspam.com/blog/dns-ttl-mx-change-propagation) explains the timing.

## What email records does Hostinger add by default?

If you use [Hostinger Email](https://iblockspam.com/spf/hostinger-email), or set it up automatically, your zone contains these records ([Hostinger](https://www.hostinger.com/support/8671319-set-up-a-domain-for-hostinger-email-manually)):

| Purpose | Type | Name | Value |
|---|---|---|---|
| Incoming mail | MX | `@` | `mx1.hostinger.com` priority 5, `mx2.hostinger.com` priority 10 |
| SPF | TXT | `@` | `v=spf1 include:_spf.mail.hostinger.com ~all` |
| DKIM | CNAME (x3) | `hostingermail-a._domainkey` (and `-b`, `-c`) | `hostingermail-a.dkim.mail.hostinger.com` (and `-b`, `-c`) |
| DMARC | TXT | `_dmarc` | `v=DMARC1; p=none; rua=mailto:...` |

When you move mail to Google Workspace, Microsoft 365 or another provider, these are the records to replace. Hostinger's Google Workspace article says to remove existing MX, SPF, DKIM and DMARC records that point to other email services, because "Conflicting records can cause delivery issues" ([Hostinger](https://www.hostinger.com/support/1583453-how-to-set-up-a-domain-for-google-workspace-email)). Keep the Hostinger DKIM CNAMEs only if you still send some mail through Hostinger Email.

## How do you add an SPF record in Hostinger?

SPF is a TXT record on `@` that lists the servers allowed to send as your domain. Hostinger says a domain should have one SPF record, because more than one causes delivery problems, and shows how to merge services into a single record ([Hostinger](https://www.hostinger.com/support/1583673-how-to-add-spf-records-for-emails-at-hostinger)). [RFC 7208, section 3.2](https://www.rfc-editor.org/rfc/rfc7208.html#section-3.2) requires the same.

1. In **Manage DNS records**, look for a TXT record on `@` starting with `v=spf1`.
2. If it exists, edit it: replace or add includes so it covers every service you send from.
3. If it doesn't, choose **TXT**, enter `@` as **Name**, paste the record as **TXT Value**, and select **Add Record**.

Example for Google Workspace, from Hostinger's article (example value): `v=spf1 include:_spf.google.com ~all`. Example for a domain using Hostinger Email plus a newsletter tool: `v=spf1 include:_spf.mail.hostinger.com include:emailmktprovider.tld ~all`. Our [SPF provider pages](https://iblockspam.com/spf) list each include, and the [SPF Record Generator](https://iblockspam.com/tools/spf-generator) builds a merged record.

## How do you add a DKIM record in Hostinger?

DKIM publishes the public key receivers use to check your messages' signatures. Your email provider gives you either a TXT record or CNAME records. Hostinger Email uses three CNAMEs; see the [Hostinger Email DKIM page](https://iblockspam.com/dkim/hostinger-email).

### DKIM as a CNAME

1. Choose **CNAME**.
2. Enter the host without your domain, for example `selector1._domainkey` for Microsoft 365.
3. Paste the provider's target as **Target (Points to)**.
4. Select **Add Record**, then repeat for each selector.

### DKIM as a TXT record

1. Choose **TXT**.
2. Enter the selector host, for example `google._domainkey` for Google Workspace.
3. Paste the key, starting `v=DKIM1;`, as **TXT Value**, in one piece with no line breaks.
4. Select **Add Record**.

Hostinger's help doesn't state a TXT length limit or how it stores values longer than 255 characters. DNS stores long values as several strings, and [RFC 6376, section 3.6.2.2](https://www.rfc-editor.org/rfc/rfc6376.html#section-3.6.2.2) says receivers join them "with no intervening whitespace." So after saving a 2048-bit key, check that the full key is published; our [2048-bit DKIM key guide](https://iblockspam.com/blog/dkim-2048-bit-key-txt-record-too-long) shows how. Then turn on signing at your provider, as covered in [DKIM setup for Microsoft 365 and Google Workspace](https://iblockspam.com/blog/dkim-setup-microsoft-365-google-workspace).

## How do you add a DMARC record in Hostinger?

DMARC is a TXT record at `_dmarc` that tells receivers what to do with mail failing SPF and DKIM alignment. Hostinger's steps ([Hostinger](https://www.hostinger.com/support/8412851-how-to-add-a-dmarc-record-for-hostinger-email/)):

1. Choose **TXT**.
2. Enter `_dmarc` as **Name**.
3. Enter your policy as the value, for example `v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com`.
4. Leave **TTL** at the default (14400) and select **Add Record**.

If a `_dmarc` record already exists from Hostinger Email, edit it instead of adding a second one. Start at `p=none`, read the reports, then tighten. The [DMARC Record Generator](https://iblockspam.com/tools/dmarc-generator) builds the record and [DMARC record examples](https://iblockspam.com/blog/dmarc-record-examples) explains the tags.

## How do you change MX records in Hostinger?

From Hostinger's [MX article](https://www.hostinger.com/support/4443666-how-to-manage-mx-records-in-hpanel):

1. Note the current MX records, or export the zone.
2. In **Manage DNS records**, choose **MX**.
3. Enter `@` as **Name**.
4. Enter the mail server hostname in **Mail server (Points to)** and the **Priority** your provider gives.
5. Select **Add Record**, and repeat for each MX host.
6. Delete the old `mx1.hostinger.com` and `mx2.hostinger.com` records.

Hostinger's Google Workspace example is priority 1, name `@`, value `smtp.google.com`, TTL 3600. For Microsoft 365, use the MX value shown for your domain in the Microsoft 365 admin center. Changing MX moves all incoming mail at once, so read [how to change MX records without losing email](https://iblockspam.com/blog/change-mx-records-without-losing-email) first.

### What does Reset DNS Records do?

**Reset DNS Records**, at the bottom of the DNS page, does what it says: "Resetting the DNS zone will revert all records to their default values" ([Hostinger](https://www.hostinger.com/support/6215812-how-to-reset-your-domain-s-dns-zone)). It's useful if a zone is beyond repair, but it removes every custom email record you added. Use **DNS history** > **Restore** to undo a single bad change instead.

## How do you check the records after saving?

Hostinger says to allow up to 24 hours for changes to propagate, though its Google Workspace article says to allow a few hours. Then check each record:

| Record | Check with | Pass looks like |
|---|---|---|
| MX | [MX Lookup](https://iblockspam.com/tools/mx-lookup) | Only your new provider's hosts |
| SPF | [SPF Checker](https://iblockspam.com/tools/spf-checker) | One record, 10 lookups or fewer |
| DKIM | [DKIM Checker](https://iblockspam.com/tools/dkim-checker) | A complete key at your selector |
| DMARC | [DMARC Checker](https://iblockspam.com/tools/dmarc-checker) | One valid record |

Then send a test message to an outside mailbox and look for `spf=pass`, `dkim=pass` and `dmarc=pass` in its headers; our [header guide](https://iblockspam.com/blog/how-to-read-email-headers) shows where.

## What are the common Hostinger email DNS mistakes?

- **Leaving Hostinger's MX records** next to the new provider's.
- **Two SPF records**: Hostinger's plus a new one.
- **Typing the full domain** in Name, such as `_dmarc.example.com`.
- **Using Reset DNS Records** to undo one change, which wipes all custom records.
- **Editing Hostinger DNS while the nameservers point elsewhere.**
- **Keeping the 4-hour TTL** during an MX move.

## Next steps

1. Export your zone, then run the [Email Health Check](https://iblockspam.com/tools/email-health-check) to see all four records together.
2. Build a single SPF record with the [SPF Record Generator](https://iblockspam.com/tools/spf-generator) and a DMARC record with the [DMARC Record Generator](https://iblockspam.com/tools/dmarc-generator).
3. Check DKIM with the [DKIM Checker](https://iblockspam.com/tools/dkim-checker) once signing is on.
4. Moving mail to Google Workspace? Our [Google Workspace platform page](https://iblockspam.com/platforms/google-workspace) explains how inbound filtering fits in front of it.

If you later point MX at a filtering service such as iBlockSpam, you use the same MX steps with its values. More walk-throughs are in [setup guides](https://iblockspam.com/blog/topic/setup).

## Frequently asked questions

### What should I put in the Hostinger Name field for the root domain?

Enter @. Hostinger's MX and TXT articles both use @ for the root domain, and its Hostinger Email setup page says you can use @ or leave the host empty. For anything else, enter only the prefix, such as _dmarc or google._domainkey, because Hostinger describes the host as the name without the domain.

### Which Hostinger Email records do I remove when moving to Google Workspace?

Remove the MX records for mx1.hostinger.com and mx2.hostinger.com, the SPF record that includes _spf.mail.hostinger.com, and the three hostingermail DKIM CNAMEs if you no longer send through Hostinger. Hostinger says conflicting records from other email services can cause delivery issues, so only your new provider's records should remain.

### What is the default TTL in Hostinger DNS?

Hostinger's TXT, CNAME, MX and DMARC articles give 14400 seconds, or 4 hours, as the default. That is a long cache time for a record you're about to change. Lower it to around 300 seconds a day before an MX move, then raise it again once the new records are confirmed.

### Can I undo DNS changes in Hostinger?

Yes. Hostinger's DNS page has a DNS history tab with a Restore option for a past date, and an export that downloads the zone as a BIND-format text file. Reset DNS Records is different: it reverts every record to Hostinger's defaults, which would remove custom email records you added.

### Do Hostinger DNS records work if my domain uses other nameservers?

No. Hostinger says records in its DNS zone take effect only when your domain uses its assigned Hostinger nameservers. If the domain points to Cloudflare or another DNS host, add your email records there. Our MX Lookup shows which nameservers your domain uses.

## Sources

- [Hostinger Help: How to manage my DNS records on hPanel](https://www.hostinger.com/support/1583249-how-to-manage-my-dns-records-on-hpanel)
- [Hostinger Help: How to manage MX records in hPanel](https://www.hostinger.com/support/4443666-how-to-manage-mx-records-in-hpanel)
- [Hostinger Help: How to manage TXT records in hPanel](https://www.hostinger.com/support/1583664-how-to-manage-txt-records-in-hpanel)
- [Hostinger Help: Set up a domain for Hostinger Email manually](https://www.hostinger.com/support/8671319-set-up-a-domain-for-hostinger-email-manually)
- [Hostinger Help: How to set up a domain for Google Workspace email](https://www.hostinger.com/support/1583453-how-to-set-up-a-domain-for-google-workspace-email)
- [Hostinger Help: How to add a DMARC record for Hostinger Email](https://www.hostinger.com/support/8412851-how-to-add-a-dmarc-record-for-hostinger-email/)
- [Hostinger Help: How to reset your domain's DNS zone](https://www.hostinger.com/support/6215812-how-to-reset-your-domain-s-dns-zone)
- [RFC 6376: DomainKeys Identified Mail (DKIM), section 3.6.2.2](https://www.rfc-editor.org/rfc/rfc6376.html#section-3.6.2.2)

## Free tools for this guide

- [MX Lookup](https://iblockspam.com/tools/mx-lookup): See where your mail is delivered, spot unfiltered backup MX and broken hosts.
- [SPF Checker](https://iblockspam.com/tools/spf-checker): Count real DNS lookups, find PermErrors, loops and risky "all" settings.
- [DKIM Checker](https://iblockspam.com/tools/dkim-checker): Validate DKIM keys by selector, including key type and strength.
- [DMARC Checker](https://iblockspam.com/tools/dmarc-checker): Check your policy, reporting and the safe path from p=none to reject.

---

Source: iBlockSpam, https://iblockspam.com/blog/add-email-dns-records-hostinger (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt