How long does it take for Hostinger DKIM records to update?

DNS propagation typically takes anywhere from 5 minutes to a few hours, though global propagation can occasionally take up to 24 hours. You can use online diagnostic tools or command-line utilities to check when the record becomes globally visible.

What should I do if my domain uses Cloudflare instead of Hostinger hPanel?

If your domain's nameservers point to Cloudflare or another external provider, editing the DNS zone inside Hostinger hPanel will not work. You must log into your Cloudflare dashboard and add the DKIM TXT record there under the DNS management tab.

Why is my email still going to spam after setting up DKIM?

DKIM is only one component of email authentication. Ensure you also have a valid SPF record and a DMARC policy configured. Additionally, check your domain and IP reputation, mailing list hygiene, and content to avoid triggering spam filters.

Can I use the same DKIM record for multiple domains on Hostinger?

No, DKIM keys are unique to each domain name and mail service configuration. If you manage multiple custom domains in hPanel, you must generate and publish a distinct DKIM record for every single domain.

What format should the public key be in when pasting into hPanel?

The TXT value should start with 'v=DKIM1;' followed by the key type and the public key string (e.g., 'k=rsa; p=...'). Ensure you paste the exact string provided by your email host without adding extra line breaks or modifying the syntax.

Hostinger DKIM Record Setup: Step-by-Step Guide

Setting up DomainKeys Identified Mail (DKIM) on Hostinger hPanel is a critical step to ensure your emails land in the inbox instead of the spam folder. DKIM adds a cryptographic signature to your outgoing messages, proving to receiving mail servers that the email genuinely originated from your domain and was not altered in transit. Without this configuration, your emails risk being flagged or rejected by modern mailbox providers like Gmail and Microsoft 365.

To verify your records are publishing correctly after making changes, you can use the DKIM Checker to instantly query your domain's cryptographic signature and spot any syntax errors before they impact your email delivery.

Understanding DKIM and Email Authentication

Email spoofing and phishing have forced mailbox providers to enforce strict authentication protocols. DKIM works alongside Sender Policy Framework (SPF) and Domain-based Message Authentication, Reporting, and Conformance (DMARC) to form a robust security triad. When you configure a hostinger dkim record setup, your email server signs every outgoing message with a private key. The receiving server looks up your public key via the DNS records you publish in hPanel to verify the signature.

If the signature matches, the email passes authentication. If you send emails through Hostinger's default email service, Titan, or point your domain's MX records to Hostinger while using custom hosting, you must manage your DNS zone settings through hPanel.

Prerequisites for Hostinger DKIM Configuration

Before you begin the hostinger dkim record setup, ensure you have the following ready:

Active Hostinger Account: Access to your hPanel dashboard.
Custom Domain: A domain name managed either through Hostinger's default nameservers or connected via external DNS.
Email Service Provider: Knowing whether you are using Hostinger Titan Email or pointing your mail flow to an external provider like Google Workspace or Microsoft 365. Note that DKIM records must always originate from the platform that generates your outbound mail.

Step-by-Step: Hostinger DKIM Record Setup

The exact procedure depends on whether you are using Hostinger's built-in Titan email hosting or a custom mail server. Below is the standard workflow for domains managed directly inside hPanel using Hostinger name servers.

Step 1: Access hPanel DNS Zone Editor

Log in to your Hostinger hPanel account.
Navigate to the Domains menu or find your target domain on the main dashboard home screen.
Click on Manage next to your domain name.
Scroll down to the Advanced section in the sidebar or main menu and click on DNS Zone Editor.

Step 2: Retrieve Your DKIM Records from Your Mail Provider

If you use Hostinger Titan Email, the DKIM records are usually pre-generated or provided inside your Titan email control panel. If you are configuring a custom mail server or forwarding service, obtain the exact TXT record host name (selector) and value string from your email provider's admin console.

A typical DKIM TXT record looks like this:

Type: TXT
Host / Name: default._domainkey (or selector1._domainkey)
Value / Points To: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQFAAOCAQ8AMIIBCgKCAQEA...

Step 3: Add the DKIM Record in hPanel

In the DNS Zone Editor, locate the section labeled Add DNS Record.
Select TXT from the record type dropdown menu.
In the Name field, enter your selector prefix (e.g., default._domainkey or titan._domainkey). Note that hPanel will automatically append your domain name to the end, so entering default._domainkey results in default._domainkey.example.com.
In the TXT value field, paste the long cryptographic public key string provided by your email host.
Leave the TTL (Time to Live) at its default setting (usually 14400 seconds or default).
Click the Add Record button.

Record Type	Host / Name	TXT Value / Content	TTL
TXT	`default._domainkey`	`v=DKIM1; k=rsa; p=MIIBI...`	Default (14400)
TXT	`selector._domainkey`	`v=DKIM1; k=rsa; p=MIIBI...`	Default (14400)

Verifying Your DKIM Setup

DNS propagation takes time, ranging from a few minutes up to 24 hours globally. Once you have added the record, verify that it is publicly visible and syntactically correct.

Using Command Line Tools

You can use dig or nslookup from your local terminal to query the TXT record directly against public nameservers like Google (8.8.8.8) or Cloudflare (1.1.1.1).

dig TXT default._domainkey.example.com @8.8.8.8

Expected output sample:

; <<>> DiG 9.16.1-Ubuntu <<>> TXT default._domainkey.example.com @8.8.8.8
;; global options: +cmd
;; questions:
;; answer section:
default._domainkey.example.com. 3600 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQ..."

If you are on Windows PowerShell, use the following cmdlet:

Resolve-DnsName -Name "default._domainkey.example.com" -Type TXT

Common Mistakes and How to Fix Them

Even experienced administrators make errors during DNS updates. Watch out for these pitfalls:

Incorrect Selector Name: Entering only _domainkey without the selector prefix (like default or titan) will cause lookups to fail. Always include the exact selector string specified by your email provider.
Extra Quotes or Truncation: Long DKIM keys often exceed standard string lengths. If you copy and paste the public key, ensure hPanel hasn't split it into multiple strings incorrectly, or that trailing spaces weren't introduced.
Conflicting Nameservers: If your domain uses external nameservers (such as Cloudflare or AWS Route 53) instead of Hostinger's default nameservers, editing the DNS zone inside Hostinger hPanel will have no effect. You must add the DKIM record at your active DNS host instead.
Missing SPF or DMARC: DKIM works best when paired with a valid SPF record and a DMARC policy. Make sure your overall authentication posture is complete.

DKIM Setup Checklist

Review this quick checklist to ensure your implementation is complete:

Identified the correct email provider and obtained the exact DKIM selector and public key.
Confirmed whether the domain uses Hostinger nameservers or external DNS management.
Navigated to the DNS Zone Editor inside Hostinger hPanel.
Added the TXT record with the proper selector name and public key string.
Verified DNS propagation using command-line tools or a dedicated lookup utility.
Sent a test email to an external mailbox and inspected the headers for dkim=pass.

How to Configure DKIM on Hostinger hPanel for Custom Domains