Custom Domain Guide

Serve your digital business card at your own web address with a clean, branded URL.

What Is a Custom Domain?

A custom domain lets you serve your digital business card at your own web address instead of the default NexaLink URL. For example:

Your visitors see a clean, branded URL that belongs to you. The card page content and features remain identical -- only the URL changes.

Prerequisites

Before setting up a custom domain, you need:

1. Higher tiers -- Custom domains are available on the higher Lifetime Deal tiers (Business and Agency). Free and Solo users upgrade once to unlock them.
2. Domain registrar access -- You need the ability to add DNS records at your domain registrar (GoDaddy, Namecheap, Cloudflare, Google Domains, etc.).
3. A domain you own -- You can use a subdomain like card.yourname.com or contact.yourcompany.com. You cannot use a nexalink.co subdomain.

Step-by-Step Setup

Step 1: Enter Your Domain in the NexaLink Card App

1. Open the NexaLink Card app on your phone.
2. Go to Settings (gear icon).
3. Tap Custom Domain.
4. Enter your desired domain (e.g., card.alexrivera.com).
5. Tap Set Up Custom Domain.

The app saves your domain and displays DNS configuration instructions.

Step 2: Add a CNAME Record at Your Domain Registrar

Log in to your domain registrar and add the following DNS record:

Example for common registrars:

• GoDaddy: DNS Management > Add Record > CNAME > Host: card > Points to: cname.vercel-dns.com
• Namecheap: Advanced DNS > Add New Record > CNAME > Host: card > Target: cname.vercel-dns.com
• Cloudflare: DNS > Add Record > CNAME > Name: card > Target: cname.vercel-dns.com (set proxy status to "DNS only")

For apex domains (e.g., alexrivera.com without a subdomain): Use an A record pointing to Vercel's IP address instead of a CNAME. However, subdomains are recommended for reliability.

Step 3: Wait for DNS Propagation

DNS changes typically take 5 to 30 minutes to propagate, though in rare cases it can take up to 48 hours. During this time:

• Your domain will show a "Pending DNS" status in the NexaLink app.
• The app automatically checks every 5 minutes for pending domains.
• You can also manually tap Verify DNS to check immediately.

Step 4: Verify in the App

Once DNS has propagated:

1. Open the NexaLink Card app.
2. Go to Settings > Custom Domain.
3. Tap Verify DNS.
4. If the CNAME record is found pointing to cname.vercel-dns.com, the status changes to Verified.
5. SSL is automatically provisioned by Vercel (this takes an additional 1-2 minutes).
6. Your card is now live at your custom domain.

Multi-Card Routing

If you have multiple cards, your custom domain supports automatic routing:

Card ordering: Index 0 is always your primary card. Subsequent indexes follow creation date (oldest first). So /1 is your second-oldest card, /2 is the third, and so on.

Fallback: If the path does not match any card by index, slug, or name, your primary card is displayed.

Troubleshooting

DNS Not Propagating

Symptom: Status stays "Pending DNS" after 30+ minutes.

Solutions:

1. Double-check your CNAME record at the registrar. The host should be just the subdomain (e.g., card), not the full domain.
2. Verify the target is exactly cname.vercel-dns.com with no trailing dot or extra characters.
3. If using Cloudflare, make sure the proxy status is set to DNS only (gray cloud), not Proxied (orange cloud).
4. Use a DNS checker tool (e.g., dig card.alexrivera.com CNAME or dnschecker.org) to verify the record is visible globally.
5. Wait up to 48 hours if your registrar has slow propagation.

SSL Errors

Symptom: Browser shows "Your connection is not private" or "SSL certificate error."

Solutions:

1. Wait 2-5 minutes after verification. SSL provisioning is automatic but not instant.
2. Clear your browser cache or try an incognito window.
3. If the error persists after 10 minutes, remove and re-add the domain in the NexaLink app.

Redirect Loops

Symptom: Browser shows "This page redirected you too many times."

Solutions:

1. If using Cloudflare, set SSL mode to Full (strict), not Flexible.
2. Ensure you do not have conflicting redirect rules at your registrar or CDN.
3. Check that you do not have both an A record and a CNAME record for the same subdomain.

Domain Shows "Not Configured" (404)

Symptom: Visiting the custom domain shows a "Domain not configured" error.

Solutions:

1. Verify the domain status is "Verified" in the NexaLink app (not "Pending" or "Failed").
2. Confirm your NexaLink subscription is still active (Premium or Enterprise).
3. If your subscription lapsed, the domain is deactivated. Resubscribe and the domain will be re-verified automatically.

Frequently Asked Questions

Can I use a subdomain?

Yes, subdomains are the recommended approach. Common choices:

• card.yourname.com
• contact.yourname.com
• me.yourname.com
• hello.yourcompany.com

Can I use an apex (root) domain?

Yes, but you need to use an A record instead of a CNAME. Subdomains are preferred because CNAME records are simpler to configure and more reliable for this use case.

Can I change my custom domain later?

Yes. Go to Settings > Custom Domain > Remove Domain, then set up a new one. Your old domain will stop working immediately, and your card reverts to the default nexalink.co URL until the new domain is verified.

What happens to my existing nexalink.co link?

Your default NexaLink URL (nexalink.co/card/{userId}/{slug}) continues to work alongside your custom domain. Both URLs point to the same card. Existing QR codes and shared links remain valid.

How many custom domains can I have?

• Premium: 1 custom domain per card.
• Enterprise: Up to 5 custom domains per account.

What happens if I downgrade from Premium?

Your custom domain is deactivated (status changes to "expired") and removed from routing. Your card reverts to the default nexalink.co URL. If you upgrade again later, you can re-verify the same domain without reconfiguring DNS (assuming the CNAME record is still in place).

Is SSL included?

Yes. SSL certificates are automatically provisioned and renewed by Vercel at no additional cost. Your custom domain always uses HTTPS.