Hostinger setup

Use this guide when Hostinger is the authoritative DNS provider for your domain. Buying the domain or email from Hostinger does not necessarily mean DNS is managed there.

Before changing DNS

1. Open Hostinger hPanel and check the domain's active nameservers.
2. Confirm the current website still works at a separate Hostinger temporary URL, staging URL, or origin subdomain.
3. Add that working address as the Origin URL in Prerender Buddy.

Do not use the public www address as the origin after it points to Prerender Buddy. That creates a request loop.

If Hostinger does not provide a suitable temporary URL, create an origin hostname such as origin.example.com that points directly to the existing hosting destination before changing www.

Point www to Prerender Buddy

In hPanel, open Domains > Domain portfolio > Manage > DNS / Nameservers and edit the DNS zone:

1Type: CNAME
2Name: www
3Target: customers.prerenderbuddy.com

Remove an existing www A, AAAA, or CNAME record if it conflicts. Do not remove unrelated records.

Handle the root domain

Redirect example.com to https://www.example.com with a permanent redirect. Preserve the full path and query string when Hostinger's redirect tool allows it.

Protect Hostinger email

Website routing does not require removing mail records. Keep existing MX, SPF, DKIM, DMARC, and mail-verification records unless your email provider explicitly tells you to change them.

Complete validation

Add any TXT validation record shown in the Prerender Buddy dashboard. Hostinger normally expects only the host portion, such as _acme-challenge.www, rather than the full domain.

DNS changes can take time to appear through public resolvers. Refresh Prerender Buddy after the record is visible, then run Verify Installation and test the exact www hostname.

Common Hostinger mistakes

• Editing DNS in Hostinger while the active nameservers point somewhere else
• Replacing or deleting email records while changing the website CNAME
• Using https://www.example.com as both public URL and origin
• Leaving a conflicting www A record in the zone
• Testing only the root domain while www is the protected hostname