Custom domain guide
How to connect a Hostinger domain to Cloudflare Pages
The exact records to add at Hostinger, written the way its form asks for them, for both www and the bare domain.
Checked 16 October 2026
In short
The records you'll add
- Type
- CNAME
- Name
- Points to
Replace the capitals with your own value from the host's dashboard.
| Type | Name | Points to |
|---|---|---|
| CNAME | Replace the capitals with your own value from the host's dashboard. |
Plus a forward from the bare domain to www (step 5).
Step by step
Set it up
- 1
Add the domain in Cloudflare Pages first
In Cloudflare Pages, go to Workers & Pages→your project→Custom domains→Set up a domain and enter your domain (for example www.example.com). Add each address separately in Custom domains.
Custom domains are included on the free plan.
- 2
Open the DNS records at Hostinger
Sign in, then go to Domains→your domain→DNS / Nameservers
The domain has to use Hostinger's nameservers.
- 3
Clear what's in the way
Domains often come with A and CNAME records pointing at Hostinger. Edit or delete the ones for @ and www before adding yours.
- 4
Add the record for www
Click Add Record and add:
- Type
- CNAME
- Name
- Points to
Replace the capitals with your own value from the host's dashboard.
Type Name Points to CNAME Replace the capitals with your own value from the host's dashboard.
- 5
Point the bare domain
Cloudflare Pages can only serve a bare domain with the domain on Cloudflare's nameservers. With your DNS at Hostinger, use www as the address and forward the bare domain to it.
Use Hostinger's forwarding (often called URL redirect or Forwarding) to send example.com to https://www.example.com, and give Cloudflare Pages the www address.
- 6
Wait, then check
Changes at Hostinger take effect within 24 hours. Once Cloudflare Pages sees the records, it issues the certificate for https by itself. Use the check below to see what the world sees.
Check your domain
Once the records are in, see whether the world can see them pointing at Cloudflare Pages.
Changes can take from a few minutes to a day to show up everywhere.
Good to know
Common snags
- Always add the domain under Custom domains first: a CNAME created by hand without it ends in a 522 error.
- If you have CAA records, they must allow Cloudflare's certificate authorities.
- To point the bare domain at a hostname, choose CNAME with the name @: Hostinger saves it as an ALIAS. Only one is allowed.
- If Hostinger's CDN is on, it manages the bare domain's records: turn the CDN off first.
Still not working?
Questions
Before you start
Should I use www or the bare domain with Cloudflare Pages?
Add each address separately in Custom domains. www always works with a single CNAME; the bare domain depends on what Hostinger offers, covered in step 5.
Why does my site show a certificate error?
The certificate is issued once Cloudflare Pages sees your records, which can take a while after DNS changes. If it stays, check for old records on the same name (parking pages, AAAA records) and, at Cloudflare, that the record is set to DNS only.
Will this affect my email?
No. Email uses MX records, which these steps don't touch. Only change the records for @ and www.
Rather skip git and build settings?
99helpers puts a file, a folder or a built site online in seconds, then a single CNAME connects your domain, with passwords, analytics and AI editing built in.
Connect a Hostinger domain to 99helpersOr skip the setup
Drop it in. It's online in seconds.
A file, a folder or a whole site: 99helpers puts it online at its own address, with no git, no build settings and no DNS to start with. Add your own domain whenever you're ready.