Custom domains
You own the domain and control its DNS. We serve the site, issue the certificate, and keep both working.
To connect one, see connect your domain.
HTTPS is automatic and free
Let's Encrypt, issued once the domain resolves here and renewed for as long as it points at us. Nothing to buy, click or remember.
The order cannot be shortcut — records, then resolution, then certificate — because issuance works by fetching a challenge over the domain itself.
Force HTTPS is on by default. Anything arriving on http:// is redirected.
One primary, everything else redirects
The primary domain serves the site. Every other domain on the same Pressy
issues a 301 to it, including your pressy.site address once you switch that
redirect on. It is what stops search engines finding two identical copies of
your site and splitting its ranking.
www is an implicit alias — connecting the apex covers it.
Removing a domain asks you to type it. The primary cannot be removed while it is primary; switch to another address first.
Your pressy.site address never goes away
Every Pressy keeps one, whatever domains you add. It is how you reach the site while DNS is propagating, and how you tell a site problem from a domain problem — see connection timed out.
What this can’t do
We only see what public DNS sees. If your computer, VPN or router cache disagrees with the internet, our reading is the internet's.
What to do: check from dnschecker.org or dig yourdomain.com. See
my domain is not pointing here.
We cannot edit records at your registrar unless it supports the automatic setup and you approve it there. We do not host DNS.
What to do: add the records yourself at whoever answers DNS for the domain, which is not always the registrar.
A CAA record blocks issuance without saying so.
What to do: check it first whenever a certificate will not issue on a domain that resolves correctly — how to check and fix it.
Let's Encrypt limits certificates per domain per week. Removing and re-adding a domain exhausts it.
What to do: add it once and leave it. Waiting is the only fix, and issuance resumes on its own.
A high TTL keeps visitors on your old host after a move.
What to do: lower the TTL to 300 before you move, not after.
You cannot upload your own certificate, and we do not sell domains or email — deliberately.
Didn’t solve it?
Write to us with your Pressy’s address and what you were doing when it went wrong. Answered by the people who built it.
Last updated