Choosing and connecting your custom domain — a non-technical guide

Why a custom domain matters

A custom domain (yourname.com) is a small, one-time decision that pays off for years. Three reasons it matters more than people expect. First, it's portable: when you switch from one platform to another, you take the URL with you. Recruiters and old contacts still find you. Second, it's a credibility shortcut — "hire-me.platform.com/yourname" reads like a side project; "yourname.com" reads like an established professional. Third, it makes email at your own domain possible later, which is another visible step up.

The cost is in the order of $10 to $20 a year for a .com, less for some other TLDs. There is no recurring "hosting" cost on top of that if you use a platform that includes hosting (Mycvify does on the Pro plan, as do most personal-site builders).

Picking a name you won't regret

The default best choice is your real name, ideally with no hyphen. firstnamelastname.com if it's available is unbeatable. If it's taken — common for short or popular names — fall back in this order: middle initial, profession suffix, country TLD.

Avoid clever puns or tools-of-the-week. "Susanship.it" was funny in 2017 and is now an embarrassment to update. Your name is the only brand that ages with you safely. If your real name is genuinely unwriteable in your audience's languages, a stable nickname you've used for years is fine.

• yourname.com — first choice if available.
• yournameportfolio.com or yourname.dev / .design / .co — common backups.
• yourname.country-code (.es, .com.ar, .com.cn) — natural if you serve a single country.
• Avoid hyphens, numbers, intentional misspellings.
• Say it out loud — if you'd hesitate spelling it on a phone, skip it.

Where to buy: registrars worth using

A domain registrar is the company that sells you the domain. Most are fine for the buying part; the difference shows up in renewal pricing, support, and how transparent they are about whois privacy and add-ons.

Three reputable choices for individuals in 2026. Cloudflare Registrar — sells at cost (around $9.77 per .com per year), no upsells, but you must keep DNS at Cloudflare and the dashboard is more technical. Porkbun — friendly UI, free whois privacy, fair renewal pricing, no parking pages. Namecheap — long-running, broad TLD coverage, free whois privacy, occasional aggressive upsell at checkout that's safe to decline.

Avoid registrars that lure you in with a $0.99 first-year price and renew at $30 — read the renewal cost before clicking buy. Equally, avoid registrars sold to you by your hosting platform if you might ever leave that platform; transferring out is easier from a neutral registrar.

Connecting it to your site: DNS in plain English

Once you own the domain, you have to tell the internet where it points. That's what DNS records do. You don't need to understand the protocol — you just need to copy two or three values from your hosting platform into your registrar's DNS settings.

The records you'll usually see are A ("apex domain points to this IP"), CNAME ("this subdomain is an alias for that hostname"), and TXT ("verification token"). Your platform tells you which records to set; you go to your registrar, find DNS settings, and paste them. Save. Wait. Done.

Propagation time used to be hours; in 2026 it is usually minutes for new records, occasionally up to an hour. If your site doesn't load after an hour, double-check that you copied the value exactly, no extra spaces or trailing dots that shouldn't be there.

On Mycvify the flow is: paste your domain into the dashboard, copy the three records we generate, paste them into your registrar, and we verify and issue an SSL certificate automatically. The principle is the same on any modern platform.

• Buy the domain at a reputable registrar.
• In your hosting platform, add the domain.
• Copy the records the platform shows (usually A + CNAME + TXT).
• In your registrar's DNS panel, paste them.
• Wait a few minutes, refresh the platform's verify button.
• SSL is issued automatically by all modern platforms — don't pay for a separate certificate.

What can go wrong (and is fine to ignore)

Common stumble: you copied the platform's CNAME target with a leading or trailing dot that the registrar UI silently keeps. Re-paste, save again. Common stumble two: you set up records on a different domain than the one you're verifying — easy when you own three. Triple-check the domain in the registrar's URL.

What's fine to ignore: warnings about DNSSEC, MX records, and SPF unless you also want email at this domain. Those are separate decisions. The website connection only needs the records the platform asks for. You can add the rest later when you're ready.