What You'll Get: A Custom Domain for Your Vercel Site

You just deployed a beautiful site on Vercel. Maybe it is a portfolio, a landing page for your SaaS, or a personal blog. Right now it lives at a forgettable URL like your-project.vercel.app. That is fine for testing, but it suggests "I just started learning." Your audience types addresses into a browser bar. They remember names, not random subdomains.

By linking your Hostinger domain to Vercel, you get a clean, professional web address: yoursite.com. No more awkward explainers. No more sharing a link that looks like a typo. And importantly, you do not need to touch a single line of code.

Vercel gives you free hosting that includes automatic SSL certificates (that little padlock icon in the browser), a global content delivery network for fast load times anywhere in the world, and seamless support for modern frameworks like Next.js, React, SvelteKit, and static HTML. The platform handles the hard parts. You only need to update a few text records inside Hostinger's control panel.

The result? Both yourdomain.com and www.yourdomain.com will work securely, redirect visitors correctly, and make you look like a pro. Total time: about 10 to 15 minutes. Seriously.

What You Need Before Starting

Let's gather the three ingredients. Missing one will cause frustration later, so check this list first.

  • A Vercel account with a project already deployed. You can have built it using Next.js, React, SvelteKit, or even a plain HTML site. If you haven't deployed yet, start by importing a GitHub repo into Vercel. It is free and takes two minutes.
  • A domain name registered through Hostinger. You need access to your hPanel, Hostinger's dashboard. If you bought the domain elsewhere, you cannot use this exact guide, but the logic is similar. Make sure the domain is active and not expired.
  • Both dashboards open in separate browser tabs. You will copy a value from Vercel, paste it into Hostinger, then return to Vercel to refresh. Tab switching saves you from logging in and out ten times.

Optional but recommended: Temporarily lower your DNS time-to-live (TTL) to 60 seconds. TTL tells internet caches how long to store a record before checking again. By default it may be set to 1 hour or longer. Drop it to 60 seconds while you make changes. That way, if you make a mistake, you can fix it and see results almost immediately instead of waiting hours. You can raise it back to 3600 (1 hour) after everything works.

That's it. No code, no command line, no developer handholding. Just three simple prerequisites.

Step 1: Add Your Domain in Vercel

Open your Vercel dashboard and click on the project you want to attach your custom domain to. Inside the project screen, look for the Settings tab on the top navigation bar. From the left sidebar, choose Domains. You will see a big button labeled Add Domain. Click it.

Type your full domain name into the text field. For example, example.com. Do not include www yet. Vercel will automatically offer to add the www subdomain as a redirect. Accept that offer. It is a best practice: the www version is technically more flexible for cookies and CDN routing, and you want both variations to point to your site. If you skip this, some visitors may see an error when they type the www version.

After you add the domain, Vercel displays the exact DNS values you need to configure. Write them down or keep this tab open. You will see something like this:

  • A record (for the root domain @): IP address 76.76.21.21 (and optionally 76.76.21.22 for redundancy)
  • CNAME record (for www): cname.vercel-dns.com

Do not close this tab. In the next step, you will copy these exact values into Hostinger. If you accidentally navigate away, you can always go back to Settings > Domains and the values will be there again.

Step 2: Update DNS Records in Hostinger

Log in to your Hostinger hPanel. On the left sidebar, find the Domains section and click Manage next to the domain you want to use. Then click DNS / Nameservers.

Hostinger likely has your domain using its default nameservers (something like ns1.dns-parking.com). Keep those nameservers. Do not change them. You are going to edit individual DNS records, not hand over control to Vercel. This is the simpler method for most people.

Now look for the list of existing DNS records. You will probably see an A record with host "@" (or left blank) pointing to some IP address. That is Hostinger's placeholder. Delete it. Then add a new A record with these details:

  • Host / Name: @ (or leave blank depending on the interface)
  • Points to / Value: 76.76.21.21
  • TTL: 60 seconds (or 3600 if you want a safer default)

If you want extra redundancy, you can also add a second A record pointing to 76.76.21.22. Many Vercel guides mention both addresses. One is usually enough, but two does not hurt.

Next, look for a CNAME record. If one exists for "www," delete it. Then add a new CNAME record:

  • Host / Name: www
  • Points to / Value: cname.vercel-dns.com (note: no trailing dot required in Hostinger's interface, but adding one never hurts)
  • TTL: 60 seconds

Double-check that you have removed any old A or CNAME records that conflict. A common mistake is leaving an old A record for the root domain alongside the new one. That creates a tie that confuses the internet. Only one A record for "@" should exist, pointing to Vercel. Similarly, only one CNAME for "www" should exist, pointing to cname.vercel-dns.com.

Save all changes. Hostinger will confirm with a green banner. You are now done on the Hostinger side.

Step 3: Verify and Wait for Propagation

Switch back to your Vercel dashboard. On the Domains page, you will see a card for your domain that likely says "Pending" or "Invalid Configuration." Ignore the message for now. Click the Refresh button next to the domain name.

Vercel will check the DNS records you just set. If everything is correct, the status will change to "Valid" with a green checkmark. Sometimes it takes a minute or two. If it stays on "Pending," wait 60 seconds and refresh again.

DNS propagation is the process of your new records spreading across internet servers around the world. Research shows that 80 percent of changes propagate within 5 minutes, and 95 percent within 15 minutes. But theoretically, it can take up to 48 hours in rare cases. Do not panic if you see "Invalid Configuration" for half an hour. Check the records using a free online DNS checker (search "DNS checker" on Google) to confirm that the A record returns 76.76.21.21 and the CNAME returns cname.vercel-dns.com.

Once Vercel detects the correct records, it automatically provisions a free SSL certificate via Let's Encrypt. This usually happens within an hour. Your site will then serve securely over HTTPS. You can confirm by visiting your domain and looking for the padlock icon.

Both your root domain and www version should work. Test both example.com and www.example.com in a browser. Vercel automatically redirects www to the root (or vice versa, depending on what you chose during setup).

Common Pitfalls and How to Fix Them

Even with simple steps, small mistakes cause big headaches. Here are the most frequent issues and their solutions.

Invalid Configuration Error That Won't Go Away

This happens when leftover DNS records conflict with the new ones. Go back to Hostinger and delete all A records except the one pointing to 76.76.21.21. Also delete any CNAME that is not pointing to cname.vercel-dns.com. Sometimes Hostinger adds a default "www" record that points to a parked page. Remove it.

Domain Not Connected After Hours

Use a public DNS checker to see what records are being served. If they still show old values, your TTL was too high. Lower it to 60 seconds, wait 5 minutes, then refresh Vercel again. If the records match but Vercel still shows red, try removing the domain from Vercel and adding it again. This forces a fresh check.

Only Root or Only www Works

You likely forgot to add one version in Vercel. Go to Settings > Domains and check whether both yourdomain.com and www.yourdomain.com appear. If one is missing, add it now. Vercel will guide you on the DNS setup for the missing version.

SSL Certificate Stuck on "Pending"

Let's Encrypt needs to verify that you control the domain by hitting a temporary file on your server. If you have DNSSEC enabled or restrictive CAA records, the verification can fail. Disable DNSSEC temporarily in Hostinger's DNS settings until the SSL is issued. Or add a CAA record that explicitly allows letsencrypt.org. After the certificate is ready, you can re-enable DNSSEC.

I Transferred My Domain Instead of Pointing It

Some people mistakenly try to transfer their Hostinger domain to Vercel. That is a different process requiring authorization codes and often fails with 500 errors. You do not want to transfer; you want to point DNS. Keep the domain registered at Hostinger and just update the records as described.

Remember: Vercel is for frontend hosting. If you need to run server-side code like WordPress or a PHP backend, keep that on Hostinger or another provider. Use Vercel for the static or serverless front end, and Hostinger for the backend if needed.

Next Steps: Going Beyond the Basics

Now that your custom domain is live, you can extend your setup without adding complexity.

Keep Your Email Working

If you use Hostinger for email (e.g., you@yourdomain.com), you need to keep your MX records intact. The process above only changes A and CNAME records, so your email should keep working. Double-check that you did not delete any MX records inside Hostinger's DNS dashboard.

Add Vercel's Analytics and Serverless Functions

Vercel's free tier includes basic analytics that show you page views and visitor geography. You can also add serverless functions (API endpoints without a server) if your site needs dynamic features like form submissions or database lookups. Both are click-to-enable in your project settings.

Explore Cloudflare as a Reverse Proxy (Optional)

Some users like to route traffic through Cloudflare for extra security and faster global DNS. You can keep Hostinger as your registrar, point nameservers to Cloudflare, and then configure Cloudflare to point to Vercel. This adds a layer of protection against DDoS attacks and can speed up page loads. It is more advanced, but the Vercel community has guides if you want to try.

Try Vercel's v0 Tool for AI-Generated Websites

If you want to build more sites quickly, Vercel's v0 tool lets you describe a website in plain English, and it generates the code for you. You can then connect a Hostinger domain using the same steps you just learned. It is a powerful way to prototype landing pages or micro-sites without a developer.

Monitor Your Site's Performance

Once everything is live, use a tool like Vercel's built-in Speed Insights to see how fast your site loads around the world. You can also link your Hostinger domain to exit intent popups or other marketing tools to capture more leads.

You now have a professional, fast, and secure website that runs on world-class infrastructure. And you did it without writing a single line of code or hiring a developer. That is the power of modern no-code hosting.

External resources: Read the official Vercel DNS documentation and the Hostinger support guide for reverse migration steps. For troubleshooting, the Vercel community forums have real user stories.

Cover photo by Milad Fakurian on Unsplash.