A 404 after connecting a domain can mean the domain reaches a server successfully but that server cannot find the requested page. That is different from a DNS failure where the domain does not resolve at all.
Check the homepage and a known inner page separately
If the homepage works but posts return 404, WordPress rewrite rules are a strong suspect. If everything returns 404, check the domain target and website root first.
Confirm the domain points to the intended Hostinger website
Review the DNS records and the website/domain assignment in hPanel. DNS changes can also take time to propagate.
Refresh WordPress permalinks
Go to Settings → Permalinks and save the intended structure again. WordPress documentation recommends refreshing permalink settings for some rewrite-related 404 problems. See WordPress common errors.
Check .htaccess and rewrite rules
If permalinks still fail, compare the rewrite configuration with the standard WordPress rules and avoid deleting unrelated hosting/security directives.
Use the host error guide when the problem is broader
Hostinger has a dedicated 404 article in its website troubleshooting section.
404 diagnosis checklist
Use the symptom to choose the next check instead of changing several settings at once. Make one change, retest the exact URL, and keep a note of what changed.
| Symptom | What it suggests | Next check |
|---|---|---|
| Homepage 404 | Domain reaches wrong document root | Check hosting assignment/document root |
| Inner pages 404 | Homepage works | Re-save WordPress permalinks |
| Only one URL 404 | Other posts work | Check the exact post slug/status |
| Temporary domain works | Custom domain fails | Check DNS and domain-to-site assignment |
Before you make a risky change
Take a current backup or restore point before editing configuration files, permissions, PHP settings or database URLs. Avoid deleting unrelated DNS, email, security or rewrite rules simply to see whether the problem disappears.
How to confirm the fix
Retest the exact public URL in a private browser window and, where relevant, on a second device or network. A fix is only confirmed when the original symptom is gone without creating a new error elsewhere on the site.
