Register a new one
You do not have a domain yet
Search, buy, done. It is registered to you and appears in your own Cloudflare account.
Live in minutes
Domains and email
Custom domains, SSL and branded email
You can put a Q-Code site on your own domain three ways: register a new one, transfer one you own, or point one you keep elsewhere.
All three take one click plus a wait for DNS. The certificate is issued automatically, usually within minutes, and the zone sits on a Cloudflare account in your name rather than ours.
Primarybike-shop.co.uk
| Type | Name | Value |
|---|---|---|
| A | @ | 104.21.x.x |
| CNAME | www | q-code.pages.dev |
| TXT | _dmarc | v=DMARC1; p=quarantine |
- DNS recordsVerified
- SSL certificateIssued
- SPF and DKIMPassing
Sending as
Three routes
Register it, move it, or leave it where it is.
Most platforms support one of these properly and make the other two your problem. All three are first-class here, because which one suits you is not something a platform should get to decide.
Transfer one you own
You have a domain elsewhere and want it all in one place
Unlock it at your current registrar, paste the auth code, approve the transfer. DNS is copied first so nothing goes dark.
5-7 days, no downtime
Point one you keep
You would rather not move the registration at all
Leave it where it is and change two records. You get the exact records to paste, and they are verified before it claims to be done.
Live in under an hour
Certificates
SSL is not a feature, it is a default.
The certificate is issued when the domain is verified and rotated before it expires. There is nothing to buy, no renewal date to remember, and no upgrade tier that unlocks it.
HTTP redirects to HTTPS, HSTS is on, and the whole site is served from Cloudflare’s edge network, which means the same certificate and the same latency wherever a visitor is.
Automatic issue and renewal
Issued on verification, rotated before expiry.
HTTPS enforced
HTTP redirects, HSTS is set, mixed content is caught by the build.
Global edge
Static files served close to the visitor rather than from one region.
DDoS protection included
Part of the platform it sits on, not an add-on.
Branded email
Mail that comes from you, and arrives.
A confirmation sent from a shared relay looks like spam because it largely is. Sending from your own authenticated domain is the difference between a receipt and a junk folder.
- Send from your own address
- Form replies, receipts, booking confirmations and broadcasts all leave from hello@your-domain rather than a shared relay nobody recognises.
- SPF, DKIM and DMARC
- All three are published and then re-checked, because one typo in an authentication record is completely silent until your mail starts landing in spam.
- A log of every send
- A message that did not arrive has somewhere to be looked up, with the reason attached.
- Receiving is your choice
- Sending is set up for you. Where your inbox lives — Google, Microsoft, anywhere — stays your decision, and the records make room for it.
Q&A
Questions about domains and email
Who owns the domain?
You do. It is registered in your name, in a Cloudflare account you hold the login to. Removing Q-Code removes the code that reads the zone; it does not touch the zone.
How long does SSL take?
Usually a few minutes after the DNS records resolve. There is nothing to buy, install or renew — the certificate is issued and rotated automatically.
Will my site go down during a transfer?
No. The DNS records are copied to the new zone and verified before the transfer completes, so the name never resolves to nothing.
Can I use a subdomain?
Yes. shop.your-domain.co.uk or app.your-domain.com are the same one-click setup as the root, and the root can keep pointing anywhere you like.
Do I need my own Cloudflare account?
Yes, and that is the point rather than a hurdle. It is free to create, it is where your domain and DNS live, and holding it yourself is what makes leaving possible without asking anyone’s permission.
Can I receive email at the domain too?
Sending is what the mail module sets up. Receiving is left to whichever provider you prefer, and the DNS records are written to leave room for it rather than to claim it.
Publish to an address that is yours.
Register a new domain, move one you own, or keep it exactly where it is. All three end with a certificate and a site that is genuinely yours to take away.