How to Connect Namecheap Domain to Hostinger Hosting Easily 2026

Before touching Namecheap, grab the nameserver addresses Hostinger wants you to use. Hostinger's own documentation points you to Websites > your site's Dashboard > Hosting plan > Plan Details, where a Nameservers card lists them; some accounts also see them on the domain's own overview panel, formatted the same way as the screenshot below.

They're listed as two addresses ending in dns-parking.com, each shown with an IP address in brackets next to it. Copy only the two nameserver addresses themselves.

Namecheap's documentation is explicit that when you're given both nameservers and IP addresses, the IP addresses don't go into the Custom DNS fields; only the ns1/ns2 hostnames do. Keep this tab open, since you'll paste these values into Namecheap in a later step.

Head to Namecheap and sign in with the account that owns the domain, not a new signup, since creating a second account won't have your domain attached to it. If you're not sure which email you used to register, check your original purchase receipt before trying to reset a password. Once you're in, the dashboard opens to your account overview, and the domain you want to redirect is listed under your active domains.

From the left-hand menu, click Domain List, find the domain you want pointed at Hostinger, and click Manage next to it. This opens the domain's settings page, split into sections for status, privacy protection, PremiumDNS, and further down, Nameservers, which is the one you need. Everything above that section (renewal status, WHOIS privacy) can stay as it is; you're only here to change one dropdown.

Click the Nameservers dropdown and choose Custom DNS instead of whatever is currently selected, usually Namecheap BasicDNS by default. This reveals empty fields where you paste the two Hostinger nameservers, one per line, in the ns1.example.tld format, with no extra spaces and no IP addresses.

Confirm with the green checkmark that appears next to the field; Namecheap will show a brief confirmation once it saves. Don't add a third or fourth nameserver unless Hostinger specifically gave you one.

The change doesn't take effect the moment you save it. Both Hostinger and Namecheap's own documentation put propagation at up to 24 hours for local ISPs to pick up the new nameservers, occasionally longer depending on your domain's prior TTL settings.

During this window it's normal for the site to load correctly on one network and show an old page or an error on another; that's caching, not a broken setup. Changing the nameserver fields again mid-wait restarts that clock, so leave them alone once they're saved.

Once propagation has had time to settle, go back into Hostinger and check the domain's status. It should flip from a pending or unverified state to active, confirming Hostinger can see the nameserver change.

If it still shows pending after a full day, double-check the exact nameserver values in Namecheap character by character; a mismatched character in a dns-parking.com address will block the connection without throwing an obvious error. Also worth checking: that an IP address didn't end up pasted into one of the nameserver fields by mistake, since that field only accepts hostnames.