ALL_POSTS

// BLOG / TRANSMISSIONS

Universal ACME Service Is Here: Trusted SSL for Every Free Domain and Host

2026-11-21

For years the padlock was the one part of a website we could not hand you. The name was free, the DNS was free, and with SEUS Free Hosting even the servers were free, but the certificate still meant another account somewhere, a DNS challenge pasted by hand, and a renewal date to dread. Every couple of months the internet quietly asked you to prove the same thing all over again, and if life got busy, the browser did the remembering for you, in red.

Today that last piece clicks in. Universal ACME Service is live as of November 21, 2026 for every free PFS domain and every free hosting instance: one unified ACME SSL service for all of them.

One thing to be clear about up front: we are not a certificate authority, and this is not a new kind of certificate. Universal ACME Service is the layer in between. The certificates come from well-known public CAs; the service gives you one door to all of them and automates everything that happens before, during, and after issuance.

What it does

The service speaks ACME, the protocol that lets a certificate be requested, issued, installed, and renewed automatically, and it runs the whole lifecycle from the same SEUS DNS console where your records already live:

  • Automated application, deployment, and renewal: request a certificate and it is issued and put to work; renewal is maintained for you, always well before expiry;
  • Automatic routing across CAs: SEUS keeps requests and renewals moving between issuers on its own, so a rate limit or a bad day at one CA does not stall yours;
  • Multiple certificates per domain: one name is not one certificate. Different services under the same domain can each carry their own cert, each deployed and renewed on its own;
  • Coverage for free hosting too: hosting instances get their certificates through the same flow, so HTTPS on your blog is one request, not a weekend project.

Certificates from four well-known CAs

To say it once more in one line: the issuing is done by Google Trust Services, ZeroSSL, Let's Encrypt, and Actalis, all of them established, publicly trusted certificate authorities. What SEUS contributes is the unified service on top: one console, one flow, and automatic routing between the four, so issuance and renewal stay reliable no matter what any single CA is doing. Your visitors see a normal, trusted padlock, exactly the one those CAs have always stood for.

Built for automation too

If you manage things the way this community tends to, you never have to open the console at all. Certificate operations work through the API and MCP, the same way the rest of SEUS DNS does, and webhooks tie certificate events into whatever automation you already run. Issue a certificate from a deploy script, let renewals happen on their own, and hear about it in your own channel when they do.

How to get yours

  1. Open the SEUS DNS console and find the domain, or the hosting instance, you want covered;
  2. Request a certificate from there, as many as the domain needs;
  3. Issuance, deployment, renewal, and the routing between CAs take it from there. Your only remaining job is running the site.

Thank you

A name, DNS to point it, a server to answer it, and now a padlock that renews itself: the whole stack is free, and every piece of it speaks the same protocol. If you put a certificate on something, show us in SEUS Community with the #PFS tag: we read everything, and your setup might be exactly what the next person was trying to build. And if PFS keeps being useful to you, a star on GitHub helps the next builder find the whole stack.