Session security
How one DNS record proves a Domain and every Site under it, where ARCY checks it, and how that keeps a third party from using up your plan's Conversations.
ARCY serves a session only from a Site under a Domain you have proven you control, and it decides which environment a call belongs to from the session itself, never from a value the caller sends. Together the two keep somebody who never touched your dashboard from using up your plan's Conversations. The dashboard steps for adding and verifying a Domain are on Domains; this page is the model behind them.
How the proof works
Proof is a DNS TXT record, the same way a certificate authority or a custom-domain feature proves ownership. For a Domain such as acme.com, ARCY issues a value unique to that Domain and your workspace, and you publish it as a TXT record named _arcy-verify.acme.com. When you press Verify, the backend looks the record up and compares it.
- One proof covers the proven name and every name under it, at any depth. Proving
acme.comcoversapp.acme.comandeu.app.acme.com, because whoever controls DNS for a name controls every name under it. No Site under a proven name needs a record of its own. - Any name can be proven. Proving
app.acme.comcovers the names under it, neveracme.comor a sibling such asadmin.acme.com, so a team that controls only its own part of the DNS can prove that part. - A Domain is a bare name.
https://www.Acme.com/pricingis saved asacme.com: the scheme, the port, the path and a leadingwww.are dropped. http and https pages on any port under the name are covered alike. - A proof belongs to the workspace and counts for every Product and every environment in it, with nothing to assign.
- A verified Domain stays verified until someone removes it. A later DNS failure never un-verifies it, and ARCY does not re-check it on a schedule. Keep the record in place anyway: it is what shows the Domain is yours.
- Nothing is added to your source code, and the proof survives redeploys.
What an unverified Domain can and cannot do
A Domain you added but have not verified is stored so you can see it is pending, and it is trusted for nothing: no Site under it starts a session on the primary environment. A workspace with no verified Domain starts no session there from a browser. There is no accidentally open state.
localhost is the one exception. It is trusted on every environment with no record, on the common development ports, so a local install works with no setup.
Where the check runs
The check runs when a session starts: the browser sends an Origin header with the request, and ARCY checks that the Site it names sits under one of your workspace's verified Domains. It is enforced on your Primary environment, which is where a production Publishable key lives; session start on any other environment accepts any Site. The browser never refuses on its own: every Site may send the request, and the answer is session start's, so a refusal always reaches the page with its reason. Every later call, a chat message, a flow step, an event, presents the session it was issued, and the backend reads the environment and the Product from that session, never from the request body. A request cannot join your Product by guessing a session id. A refused start is recorded, so a Site that fails to start a session shows up as a verdict on Installation rather than as silence.
Forgotten Sites
Covering every name under a proof has one cost. If a name under your Domain, such as old.acme.com, still points at a hosting service you stopped using, and someone claims it there, the pages they serve can start sessions with your production Publishable key. They get a session and nothing more: no Secret key, no verified identity and no data. The cost is junk sessions and the Conversations they count against your plan. Each Domain on Domains lists the Sites seen under it with the Product their traffic came from, so an unexpected Site shows up there. Delete the dangling DNS record to close it.