Use one already set up
You already hold a domain in your own Cloudflare account
Attach it in one step and wait for DNS to catch up. Nothing is bought or registered; this connects a domain you already have.
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: use one already set up in your own Cloudflare account, delegate one you own elsewhere, or point one you keep exactly where it is.
Each route is one step plus a wait for DNS to catch up. The certificate is issued automatically once DNS resolves, 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
hello@bike-shop.co.uk
Three routes
Use it, delegate 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.
Delegate one you own
You have a domain elsewhere and want DNS managed from your own Cloudflare account, without moving the registration itself
Change the nameservers at your current registrar to point to the new zone. DNS is copied over first so nothing goes dark.
No downtime while DNS updates
Point one you keep
You would rather not move the registration or the nameservers 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, whether that is Google, Microsoft or anywhere else, stays your decision, and the records make room for it.
None of the three authentication records is invented here. They are the published internet standards, and the records written into your zone follow them:SPF, RFC 7208,DKIM, RFC 6376 andDMARC, RFC 7489.
Q&A
Questions about domains and email
Who owns the domain?
You do. It stays registered wherever you registered it, and the DNS zone sits 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, because the certificate is issued and rotated automatically.
Will my site go down while I delegate a domain?
No. The DNS records are copied to the new zone and verified before the delegation 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.
Does the domain matter for AI and agents?
Yes, in two ways. A stable address is what makes a page worth citing, because a URL that moves is a citation that breaks. And the last rung of the agent-readiness scan lives in the DNS zone rather than in the site: discovery records need DNSSEC on the zone, and serving a Markdown version of a page to agents is a Cloudflare zone setting on the Pro plan and above. Holding the zone yourself is what makes either of those your decision.
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.
Use a domain you already hold, delegate one you own elsewhere, or keep it exactly where it is. All three end with a certificate and a site that is genuinely yours to take away.