Ordnary

Docs Ordnary Web Services Ordnary R2

Public access and domains

Serving objects without credentials: turning on public access, claiming an Ordnary subdomain, and attaching your own domain with two DNS records.

5 min readBeginner

Turn on public access

Under the bucket's Settings, Public access, choose Enable. From then on every object in the bucket can be read by anyone with its URL, through the bucket's public domain. Writing still needs your access key. Turn it off again at any time; the domains stop serving immediately.

An Ordnary subdomain

Pick a label and your files are served from <label>.r2.ordnary.com. Nothing to configure and nothing to wait for; it works the moment you claim it. You can claim it on the create form or later under Settings, Public domain. A bucket has one public hostname, so an Ordnary subdomain and a custom domain cannot be combined on the same bucket.

Labels are 3 to 63 lowercase characters, digits and hyphens. Names that are part of the service, such as s3 or customers, and common names such as www or api are reserved.

Your own domain

  1. 1

    Add the hostname

    Under Settings, Public domain, choose Use a domain you own and enter the hostname, such as files.example.com. Public access must be on.

  2. 2

    Create the CNAME record

    At your DNS provider, point the hostname at the target the console shows, customers.r2.ordnary.com. This routes traffic.

  3. 3

    Create the TXT record

    Add the TXT record the console shows. It proves you control the domain, so a certificate can be issued.

  4. 4

    Wait for Active

    Validation usually takes a few minutes once both records resolve. The status on the page goes from Pending to Active.

DNS records (values come from the console)
files.example.com.          300  IN  CNAME  customers.r2.ordnary.com.
<txt record name>           300  IN  TXT    "<txt record value>"
StatusMeaning
PendingWaiting for the records. Check them with dig and allow for DNS propagation.
ActiveThe hostname serves the bucket over HTTPS.
ErrorValidation failed, usually a wrong or missing record. Fix it; validation retries on its own.

What is served

https://<domain>/<key> returns the object with its content type. A missing object returns an Ordnary-branded 404 page. Set a CORS policy if browsers on other origins fetch objects with scripts. If your domain is already on a CDN or proxy, set the CNAME to DNS-only so it is not proxied twice.

Can I use the apex domain, like example.com?

Only if your DNS provider supports CNAME flattening or ALIAS records at the apex; standard DNS does not allow a CNAME there. A subdomain such as files.example.com always works.

Does the certificate renew?

Yes, automatically, as long as the records stay in place.

Can I remove the domain?

Yes, under Public domain. Remove the DNS records afterwards, or leave the CNAME and the hostname shows the 404 page.

Was this page helpful?
Updated 25 October 2026 Suggest an edit

Choose which cookies Ordnary may use. You can change this at any time via Cookie settings at the bottom of every page.