.co.uk for UK indie hackers in 2026: the domain and DNS walkthrough
Key Takeaways
- Nominet rules differ from ICANN rules - .co.uk has no standard WHOIS privacy for sole traders and limited companies.
- Cloudflare charges at-cost (around GBP 8/year for .co.uk), Namecheap and 123-Reg run 30-50% margin with renewal uplift.
- First-day mail setup requires three DNS records: SPF, DKIM, DMARC. Set DMARC to p=none on day one, tighten to p=quarantine after a week of monitoring.
- Transferring a .co.uk uses IPS tags, not auth codes. Transfer completes in 24 hours with no downtime if DNS is mirrored in advance.
- For a UK-only SaaS, .co.uk signals UK-native trust; for any international aspiration, .com is worth the GBP 8 extra a year.
Nominet is not ICANN. That one sentence makes every generic "best domain registrar 2026" article incomplete for a UK indie hacker buying a .co.uk. The rules are different, the WHOIS privacy is different, the transfer protocol is different, and in 2026 the best combination of registrar + DNS + mail setup looks different from the US default.
This is the walkthrough for a UK indie hacker buying and wiring a fresh .co.uk on day one of a new SaaS. Every step is priced in GBP, every tool is modern (Vercel, Cloudflare, Resend), no legacy UK registrar quirks are hidden. Let's go.
The TLD choice: .co.uk, .uk, .com, .io
Four candidates for a UK SaaS in 2026. Quick table.
| TLD | Recognition | Price (2026) | Registry | Best for |
|---|---|---|---|---|
| .co.uk | Very high in UK consumer market | GBP 7-15/yr | Nominet | UK-only consumer SaaS |
| .uk | Moderate | GBP 6-14/yr | Nominet | Short-brand UK SaaS |
| .com | Universal | GBP 9-12/yr | Verisign | UK-based, global ambition |
| .io | High with developers, low with consumers | GBP 35-60/yr | Identity Digital | Dev-tools, global-first |
Decision framework: if your UK customers would recognise your brand by typing it into Google, .com and .co.uk are interchangeable. If they would type the URL, pick the one that feels most natural in their head - which for UK consumers is almost always .co.uk.
For IdeaStack-style content sites with weekly fresh reports, .co gives a subtle "international media" feel. For RentSOS-style legal-tech consumer tools, .co.uk signals UK-only and immediately answers the question "does this work in Scotland?" (No, it's .co.uk because it is England-focused.)
Registrar comparison (2026, in GBP with VAT)
Five registrars a UK indie hacker realistically considers in 2026. All prices VAT-inclusive.
Cloudflare Registrar
- Price: at-cost. For .co.uk that is around GBP 8/year in 2026.
- UI: minimal, clean, integrates with the rest of the Cloudflare dashboard.
- WHOIS privacy: free where the TLD allows. For .co.uk, subject to Nominet rules (below).
- DNS: must use Cloudflare DNS. For most UK indie hackers this is what they wanted anyway.
- Lock-in: none beyond the DNS requirement.
- Best for: UK indie hackers running Vercel + Cloudflare who want the cheapest ongoing cost.
Namecheap
- Price: first-year discount (often GBP 5-7), renewal around GBP 12-14.
- UI: UK-friendly. Good enough.
- WHOIS privacy: free on generic TLDs. For .co.uk, subject to Nominet rules.
- DNS: can use Namecheap DNS, Cloudflare, or external.
- Lock-in: none.
- Best for: indie hackers who want a bundle (domain + hosting + email) under one control panel.
123-Reg
- Price: often GBP 8-12 first year, GBP 14-18 renewal.
- UI: dated. UK-native but shows its age.
- WHOIS privacy: charged extra (often GBP 5-8/yr). Nominet rules apply.
- DNS: 123-Reg DNS or external.
- Lock-in: some friction on outbound transfers.
- Best for: non-technical UK founders used to UK-brand UX.
GoDaddy UK
- Price: aggressive first-year, heavy renewal uplift.
- UI: cluttered with upsells.
- WHOIS privacy: charged extra.
- DNS: GoDaddy DNS or external.
- Lock-in: considerable friction; upsell-heavy support flow.
- Best for: avoid for an indie SaaS in 2026.
Gandi
- Price: GBP 14-18/year. More expensive but stable.
- UI: developer-friendly, EU-native.
- WHOIS privacy: included.
- DNS: Gandi DNS or external.
- Lock-in: none.
- Best for: developers who want EU-billed domain services with solid DNS.
Pragmatic pick for a UK indie hacker in 2026: Cloudflare if you are running Vercel/Cloudflare Pages, Namecheap if you want registrar-agnostic flexibility, Gandi if you need EU billing and solid DNS without Cloudflare-lock.
Avoid GoDaddy. 123-Reg is fine if you are already there and you do not want to transfer.
The Nominet WHOIS quirk on .co.uk
Here is the thing a US walkthrough misses.
Nominet's WHOIS policy (2026) is:
- Private individuals can apply for a privacy opt-out that removes their address from public WHOIS. The name still shows; the address does not.
- Limited companies, LLPs, and partnerships must show the business address. No opt-out.
- Sole traders operating under a trading name show the trading name and the natural-person address unless they opt out as individuals.
Practical implications for a UK indie hacker.
If you are a sole trader launching under your own name
Register the domain as an individual. Apply for the privacy opt-out after registration (free at nominet.uk in your account settings). Your name appears on WHOIS, your address does not.
If you are a sole trader launching under a trading name
Same as above - register as an individual, opt out of address display. The trading name can appear on your site but WHOIS will show your legal name.
If you have incorporated already
Register the domain under the Ltd company. The company's registered office appears on WHOIS. If your registered office is a service address (provided by Companies House-listed registered-office services for around GBP 60/year), this is totally neutral.
If you have not incorporated but will soon
Register as an individual with the privacy opt-out. After incorporation, transfer the domain registrant to the Ltd company. Minor paperwork step, no downtime.
First-day DNS setup for Vercel, Cloudflare Pages, and Resend
Day one DNS on a fresh .co.uk. Three destinations to cover, each distinct.
Vercel (Next.js site)
Approach 1 - Cloudflare fronting Vercel:
Type Name Value Proxy
A @ 76.76.21.21 Proxied
CNAME www cname.vercel-dns.com Proxied (or DNS only)
Approach 2 - Cloudflare nameservers, Vercel direct (no proxy):
Type Name Value Proxy
A @ 76.76.21.21 DNS only
CNAME www cname.vercel-dns.com DNS only
Approach 1 gives you Cloudflare's DDoS and caching in front of Vercel; Approach 2 is simpler but loses edge caching before Vercel. For most UK indie hackers, Approach 1 is the default.
Cloudflare Pages
Type Name Value Proxy
CNAME @ <your-project>.pages.dev Proxied
CNAME www <your-project>.pages.dev Proxied
No Vercel alternative to compare - Cloudflare-native. Simpler, cheaper for static/edge-heavy workloads.
Resend for transactional email
Three records. Values come from your Resend dashboard when you add the domain.
Type Name Value TTL
TXT @ v=spf1 include:_spf.resend.com ~all Auto
TXT resend._domainkey <DKIM key from Resend> Auto
TXT _dmarc v=DMARC1; p=none; rua=mailto:you@yourdomain.co.uk Auto
Walk-through of what each does:
- SPF (Sender Policy Framework): tells receiving mail servers which IPs are allowed to send on your behalf.
~allis a soft fail; tighten to-allafter a week of monitoring. - DKIM (DomainKeys Identified Mail): cryptographic signature that proves the email was sent with your key. Resend handles generation; you paste the public key into DNS.
- DMARC (Domain-based Message Authentication): policy that tells receiving servers what to do if SPF or DKIM fail.
p=nonefor monitoring on day one; tighten top=quarantineorp=rejectafter a week of clean delivery.
Verify the setup with dig (on macOS/Linux) or nslookup (on Windows). Or use dmarcian.com for a browser-based check.
The 30-minute ship checklist
Domain to live site in 30 minutes on a fresh .co.uk.
- Register the
.co.ukat Cloudflare Registrar (GBP 8/yr). - In Cloudflare DNS, add the A + CNAME for Vercel (or CNAMEs for Cloudflare Pages).
- In Vercel (or Cloudflare Pages), add the custom domain and confirm SSL certificate provisioning.
- Enable DNSSEC in Cloudflare (one click).
- If sole trader, apply for Nominet WHOIS opt-out in your account settings.
- Add the Resend SPF, DKIM, DMARC records.
- Verify the domain in Resend.
- Send a test email to your Gmail and check the DKIM/SPF/DMARC headers.
- Add the domain to your Plausible or Vercel Analytics project.
- Tweet/post a screenshot of the working site (optional, but good for the UK indie-hacker community).
End of that checklist, you have: a fresh .co.uk, DDoS-protected, with DNSSEC, Vercel-served, Resend-mail-ready, Nominet-privacy-configured, and monitored.
Five failure modes UK indie hackers hit
1. Registering under a trading name without opting out of WHOIS
Your home address appears on the public WHOIS. A bit awkward. 10-minute fix.
2. Setting SPF -all on day one
Hard-fails any mail that fails SPF, which includes legitimate mail from aliases or forwarders. Always start ~all (soft fail), monitor for a week, then tighten.
3. Mixing Cloudflare Registrar with non-Cloudflare DNS
Cloudflare Registrar requires Cloudflare DNS. Trying to use Route 53 or Vercel DNS on a Cloudflare-registered domain will not work.
4. Forgetting DMARC
SPF and DKIM without DMARC means you have authentication but no policy. Some receiving mail servers (Gmail in particular from 2024 onwards) flag DMARC-absent senders harder. Always set at least p=none with a rua= reporting address.
5. Using Namecheap DNS but forgetting to update nameservers
A common Namecheap gotcha: buying the domain and thinking it is immediately live. Namecheap hands you parking nameservers by default. Switch to Namecheap BasicDNS or to Cloudflare nameservers explicitly.
Transferring a live .co.uk from 123-Reg to Cloudflare
IPS tag based, not auth code based. Steps:
- At Cloudflare, start the transfer process and note the new IPS tag required (
CLOUDFLARE). - At 123-Reg, change the IPS tag on the domain to
CLOUDFLARE. - Cloudflare accepts the transfer (usually within 15 minutes).
- Propagation completes within 24 hours.
Before starting, mirror DNS records at Cloudflare so nothing drops during the tag change. Do the transfer out of hours.
Frequently Asked Questions
Should I buy .co.uk or .uk or .com for a UK-only SaaS?
Depends on audience. For a UK-only consumer-facing SaaS (renters, personal finance, local services), a .co.uk still reads as trustworthy and UK-native - Nominet tells us 85% of UK consumer brands use it. For a UK-based B2B SaaS with any international aspiration, .com is worth the extra GBP 8 a year for universal recognition. The short .uk is valid and indexes fine, but it has less mindshare than either .co.uk or .com. Avoid .io for a UK-native product - it reads as global dev-tool, not UK-specific, and it carries no SEO advantage. A useful rule: if your customers would type your brand name into Google rather than a browser bar, .com or .co.uk are interchangeable; if they would type the domain, choose the one that matches what feels most natural.
Why does Cloudflare charge less than Namecheap for a domain?
Cloudflare registers domains at cost - whatever the registry charges, that is what Cloudflare charges you. For .co.uk that means around GBP 8/year in 2026. Namecheap and 123-Reg run margin on top (often 30-50%) plus first-year discounts that bounce back to standard rates on renewal. The catch with Cloudflare is that domains registered there must use Cloudflare DNS. If you are running a Vercel site with Cloudflare DNS sitting in front (which most UK indie hackers end up doing anyway), that is not a restriction - it is the setup you wanted. If you need to use Route 53 or another DNS provider, Cloudflare is not for you.
What is the WHOIS privacy quirk on .co.uk?
Nominet rules require that the registrant's address appears on the public WHOIS unless the registrant is a private individual. Sole traders, limited companies, and partnerships all have address details publicly visible. Private individuals can apply for a privacy opt-out. Practical implication: if you are a sole trader buying a .co.uk, your home address may appear on WHOIS. Two workarounds: register as a private individual and apply for the privacy opt-out (free), or register through a limited company (which will show the company address). Most UK indie hackers who intend to incorporate eventually end up registering under the Ltd company from day one. See [the side-project to UK Ltd company walkthrough](/blog/side-project-to-uk-ltd-company-2026) for timing.
Do I need to configure DNSSEC on a .co.uk?
Not strictly required, but recommended in 2026. DNSSEC protects against DNS spoofing attacks - a relevant risk for any SaaS that handles authentication or payments. Nominet supports DNSSEC on .co.uk. Cloudflare enables it by default on domains registered with them. Namecheap requires manual activation. 123-Reg charges extra. If you are using Cloudflare (recommended), it is already on. If not, toggle it in your registrar control panel. Takes one click and the DNS propagation happens in the background.
Can I transfer a .co.uk from 123-Reg to Cloudflare mid-product?
Yes, the transfer process for .co.uk is IPS-tag based rather than auth-code-based like generic TLDs. Steps: at 123-Reg, request an IPS tag change to CLOUDFLARE. At Cloudflare, initiate the transfer using the new IPS tag. The transfer usually completes within 24 hours with no downtime if DNS records are already identical. Before transferring, mirror your DNS records at Cloudflare and point name servers there - that way the actual tag change is a paperwork step, not a live-service one. For a running SaaS, do the transfer out of hours (Sunday evening UK time) to minimise risk if a record is missing.
Topics
