Domain & PSL progress

We submit a suffix to the Public Suffix List (PSL) once it crosses the activity threshold (default: 200 approved domains AND 1500 active DNS records). After PSL approval, eligible users can unlock NS records (i.e. point their domain at Cloudflare / ClouDNS / etc.) — see /domains/[id]/records for the unlock card. Thresholds and timeline are operational; see /tos and /aup for policy.

.ac.chat

shared suffix; ‘.‘+label is your domain

PSL: Not submitted

Approved domains0 / 200

Active DNS records0 / 1500

.edu.rich

shared suffix; ‘.‘+label is your domain

PSL: Not submitted

Approved domains1 / 200

Active DNS records1 / 1500

.ii.pe

shared suffix; ‘.‘+label is your domain

PSL: Not submitted

Approved domains1 / 200

Active DNS records1 / 1500

.net.rich

shared suffix; ‘.‘+label is your domain

PSL: Not submitted

Approved domains3 / 200

Active DNS records3 / 1500

.pa.ax

shared suffix; ‘.‘+label is your domain

PSL: Not submitted

Approved domains1 / 200

Active DNS records1 / 1500

What is PSL and why does it matter?

The Public Suffix List (PSL) is consumed by browsers / certificate issuers / cookie engines to decide where one site ends and another begins. After a suffix like net.rich is on the PSL, alice.net.rich and bob.net.rich are treated as fully separate registrable domains — cookies don't leak between them, and browsers won't accept dommate-controlled cookies set on .net.rich. We submit shortly after a suffix shows real traction so individual users get this isolation.

See ToS §8 for PSL motivation disclosure.