Domain owner access
Owner access lets your customers manage protection for their own domains with Website protection at owners.stillorigin.app, without a stillorigin account. Your billing system, control panel or your own code asks the stillorigin API for a one-time sign-in link, and the domain owner signs in with it. Each link opens one domain. If you use WHMCS, the free WHMCS module gives your clients a Manage protection button that does this for you. On cPanel servers, the origin agent installs the free cPanel plugin, which adds a Manage protection page to cPanel.
The owner area is a stillorigin-branded site with no stillorigin support. Your customers get help from you, through the support link you set.
Which domains have owner access
Owner access comes with every domain with Website protection, including the Website protection licence included with each sentry. A domain without Website protection has no owner access. See Network protection vs Website protection and Licences.
Setting up owner access
Open Owner access from the menu at the bottom of the sidebar (your email and account name). The page is headed Domain owner access.
Only an account owner can change these settings or use Test owner login. Other users on your account can see the page but can't change it.
What domain owners can change
Every permission is off by default, except Captcha Protection and country blocking, which are on by default. While none is allowed, the page shows: Owners can only view their site's protection until you allow at least one setting.
Under What domain owners can change, tick the settings you want to allow, then click Save:
-
Switch Website protection rules between log mode and blocking: the owner can move their site between log mode and blocking on the Settings tab, under Website protection rules, just like Website protection rules on Edit domain.
-
Block AI crawlers, SEO crawlers and scripts: the owner can choose to block AI crawlers, SEO and marketing crawlers, and Scripts and HTTP libraries. Search engines such as Google and Bing are never blocked, and neither are certificate checks. Bot blocking always blocks, even while Website protection rules are in log mode. Blocked requests get a 403 and show in your logs as bot-ai, bot-seo or bot-scripts.
-
Set their own rate limit: the owner can set how many requests a second each IP address can make to their site, and the burst, up to your caps.
-
Lock their WordPress login page and admin area to IP addresses they choose: on WordPress domains, the owner can turn the admin login lock on or off and change its list of allowed IP addresses, but only while you haven't turned the lock on yourself. A lock you turn on stays yours: owners can't change the list or turn it off, even with this permission. They can set their own lock once yours is off. The lock always blocks, even while Website protection rules are in log mode.
-
Block identified services, such as AI crawlers, on their domain (domains with Website protection only): the owner can block a whole group or a single service we identify by its official IP addresses, on their Website protection domain only. This comes with the Website protection licence. They see Block AI crawlers and other services on the Settings tab. Your blocks are shown ticked and marked Blocked by your host, and they can't change them; they can only add blocks of their own. Blocked requests get the stillorigin block page and show in your logs as blocked by owner. This always blocks, even while Website protection rules are in log mode. If they block a search engine, they have to tick I understand, block them first. They can't turn Block fake crawlers on or off; that's yours, on Block identified traffic. This is separate from Block AI crawlers, SEO crawlers and scripts, which still blocks by user agent as a fallback, and from default blocks, which owners can allow without this permission.
-
Let domain owners change Captcha Protection on their domain, including Under Attack: this is on by default. The owner can turn Under Attack on or off in the owner area header, and on the Settings tab, under Captcha Protection, choose Use my host's settings or Choose my own checks. They can't turn off Under Attack that you turned on. If you untick the permission, you manage Captcha Protection yourself; the owner then sees Your host manages Captcha Protection for your site. Their choices are paused until you allow it again.
-
Block or check visitors by country on their domain (domains with Website protection only): this is on by default. The owner gets a Countries tab where they can add countries for their site, as a block or a Captcha Protection check, starting in log mode. Countries you set show as Blocked by your host, Checked by your host or Logged by your host, and can't be changed. If you untick the permission, the owner sees Your host manages country blocking for your site. and their countries are paused. See Country blocking.
The permissions apply to every domain owner in your account.
Rate limit caps
If you allow owners to set their own rate limit, you can cap it with Highest requests per second an owner can set and Highest burst an owner can set.
Leave these empty to cap owners at each cluster's Website protection rate limit. An owner's own rate applies to their site alone, instead of being shared with your other sites on the sentry.
Without an owner limit, a site shares the cluster's Website protection requests per second and Website protection burst with your other Website protection sites on that sentry: each IP address gets one allowance across all of them. When an owner sets a requests per second value, their site gets its own allowance for each IP address instead. If an owner sets only a burst, the site stays on the shared limit. The WordPress login limit and the connection limits always apply.
Paused settings
If you take a permission away, the owner settings that use it stop applying, but they're kept. They apply again if you allow it later. Domain owners see which settings you've paused. If you take away identified traffic blocking, the owner sees their previous choices under Your blocked services. If you take away Captcha Protection, they see Your Captcha Protection choices are paused because your host now manages Captcha Protection. They come back if your host allows changes again. If you take away country blocking, they see Your country rules are paused because your host now manages country blocking. They come back if your host allows changes again.
The same happens if you lower a cap below what an owner has set. The domain goes back to your cluster's settings, and the owner sees the setting under Settings your host has paused, on Overview and Settings. If you turn Website protection off for a domain, its owner settings are kept too, and apply again when Website protection is back on.
Default blocks for owners
On Settings › Identified traffic, under Default blocks for your clients' domains, you can block a service, or a whole group, on your clients' domains with Website protection by default. For example, you can block AI crawlers, which also covers AI services we add later. Tick Block the whole group by default, or tick single services. Defaults on the All clusters tab apply to every cluster in your account, now and in future. A cluster tab can only add defaults for that cluster; defaults for all clusters are shown ticked and can only be changed on the All clusters tab.
Visitors from a blocked service get the stillorigin block page (403), logged as blocked by default. Defaults always block, even while Website protection rules are in log mode. They don't apply to domains without Website protection.
Domain owners don't need the block identified services permission to allow a default. In their owner area, on the Settings tab, the services appear under Blocked by default by your host, each with an Allow button. Before they can allow a service, they see this notice and have to tick the box:
Before you allow this service
Your host blocks this service on your site by default. Your sentry still rate-limits crawlers, but bots from outside services can send a lot of traffic. Letting them in can slow your site down, use up its resources, or take it offline. Check your hosting terms before allowing access, because some plans limit or don't allow this kind of traffic.
The tick reads I understand, allow access. Once they've allowed a service, they can change their mind with Block again. An owner's allow is kept if you later remove the default. If an owner who has the block permission then blocks a whole group, that still blocks a service they allowed. Each allow, block again and change you make to the defaults is recorded in your audit log.
These defaults are separate from the network blocks on the same page. A network block drops the connection for every domain, with or without Website protection, and owners can't allow it. A service you block on your network is shown as Already blocked on your network in your defaults, and as Blocked by your host in the owner area, and stays locked. Hard network blocks always win.
If you're about to block a search engine by default, the page warns you that blocked search engines can't crawl your clients' sites, so their pages can drop out of search results. Click Block anyway if you're sure. Click Save defaults to apply your changes. Sentries pick them up within a minute.
Support link for owners
Under Support link for owners, enter the address of your own help page or support form. It must start with https://.
Domain owners see this link as "Get help from your host". stillorigin doesn't offer support to domain owners, so link to your own help page or support form. If you leave it empty, owners don't see a help link.
Domain owner help pack
The Domain owner help pack is a set of ready-made articles you can add to your own knowledge base, so your customers can learn how stillorigin protects their website and how to use the owner area. The articles name stillorigin and its pages, because that's what your customers see.
To get it, open Downloads in the portal menu and click Download the pack. The zip has each article as Markdown, HTML and plain text, plus a changelog. The card shows the latest version and what changed in it.
The pack covers:
- signing in to the owner area
- what Website protection does
- reading traffic and blocks
- log mode and blocking
- the browser check visitors may see (Captcha Protection)
- locking the WordPress login
- blocking countries and AI crawlers
- why a visitor was blocked, and how they get unblocked
Placeholders
The articles can include these optional placeholders:
{{HostName}}: your business name.{{SupportURL}}: your support page or form. Use the same address as your support link for owners.{{OwnerAreaURL}}: the owner area's address,https://owners.stillorigin.app.
Each placeholder sits in brackets, for example "your host ({{HostName}})". Fill it in, or delete it along with its brackets. The articles read fine either way.
Keeping the pack up to date
When you download the pack from the Downloads page, stillorigin remembers which version you have. The card then shows whether you have the latest version, and what's changed since yours. When a new version comes out, we email the account owners who downloaded an earlier one.
The pack is also at a public download link, but only downloads from the Downloads page count for update emails.
The owner area, the visitor check page and the block page are stillorigin-branded, and the pack doesn't change that. See What domain owners see.
What domain owners see
Even with every permission off, a domain owner who signs in sees their site's protection. The header shows the site name, a Website protection badge, and Website protection rules: Log mode or Website protection rules: Blocking. If you've set a support link, they also see Get help from your host. They can Sign out.
Under Attack is in the header. If you've allowed Captcha Protection, they can turn it on or off there, unless you turned it on: then they see Your host turned on Under Attack for your site. Contact your host if you need it turned off. and they can't turn it off.
The owner area has six tabs: Overview, Traffic, Blocks, Protection, Countries and Settings.
Overview shows the last 24 hours: Allowed requests, Blocked requests, Browser checks passed, 24h and Browser checks failed, 24h when Captcha Protection applies, Top block reason, 24h, and Would have blocked when the site is in log mode, or Recorded but let through when the site is set to blocking and something was recorded. If you've paused a setting, Settings your host has paused appears here too.
Traffic shows Traffic, last 24 hours: allowed and blocked requests on a chart. If there's no traffic, it reads No requests were recorded in the last 24 hours. Below the chart is a map of requests by the visitor's country: Requests to your site, by the visitor's country. No IP addresses are stored or shown here.
Blocks shows Why requests were blocked: each reason in plain words, for example Request for a private file or Database attack (rule 942100). Error pages from the site itself, such as a 404, aren't blocks, so they aren't listed. An error from stillorigin without a more specific reason shows as Error response (403) (or another number). It also shows Most blocked IP addresses, with each address's location (city and country). If nothing was blocked, it reads Nothing was blocked in the last 24 hours. When the site is in log mode, this tab also shows Would have blocked, last 24 hours. When the site is set to blocking and something was still recorded, it shows Recorded but let through, last 24 hours instead, with country rules in log mode and rules recorded before the switch to blocking labelled, the same as on the domain's Blocks tab in the portal (see After you switch to blocking).
Protection is read-only: What's protecting your site right now. You can change some of these in Settings. Your host manages the rest. It lists Website protection rules, Captcha Protection, Admin login lock (on a WordPress site), Bot blocking, Block AI crawlers and other services (if you've allowed that permission), and Rate limit. Where you've allowed a change, an Edit link opens the matching section of Settings. Where you haven't, the owner sees a note such as Your host manages this setting., Your host manages Captcha Protection for your site., Your host manages bot blocking for this site. or Your host manages rate limits for this site. On a WordPress site, if you've turned on its admin login lock, they see that the lock is on, even if you've allowed them to set it, and they can't change it. For identified traffic the owner has blocked, Protection shows You haven't blocked any services., You block 1 service or group., or You block {n} services or groups.
Countries is where they block or check visitors by country. Countries you set show as Blocked by your host, Checked by your host or Logged by your host, and they can't change them. They can add their own countries, each as a Block or a Captcha Protection check, starting in log mode, then switch a country to Enforce. See Country blocking.
Settings is where they change what you've allowed. Settings on this page jumps to the sections that apply: Captcha Protection, Website protection rules, Admin login lock (on a WordPress site, when you've allowed it and you haven't locked the login yourself), Blocked by default by your host, Block AI crawlers and other services, Bot blocking, and Rate limit. Sections you haven't allowed don't appear, except Website protection rules (which then reads Your host manages this setting.) and Captcha Protection (which then reads Your host manages Captcha Protection for your site. and still shows whether Under Attack is on, which checks apply, and the last 24 hours of checks). If you haven't allowed bot blocking, rate limits, or both, they also see a line such as Your host manages bot blocking and rate limits for this site.
Times in the owner area are shown in UTC.
When an owner saves a change, they see Saved. Changes take effect within a few minutes.
Test owner login
Use Log in as domain owner or Test owner login to see the owner area exactly as a domain owner sees it.
Open the owner area for one of your domains with Website protection, as its owner sees it. It opens in a new tab and you stay signed in here. Changes you make there apply to the live domain.
On a Website protection domain's page, an account owner can click Log in as domain owner in the header. The same button is on Edit domain, under Domain owner access.
You can also use Test owner login on Owner access:
- Choose the Website protection domain.
- Click Create test login link.
- Click Open the owner area. The link works once, within a few minutes.
The owner area shows a banner: You're using a test owner login. Changes you make here apply to the live site.
Only an account owner can use Test owner login. If you don't have any domains with Website protection yet, the page says: You don't have any domains with Website protection yet. Turn on Website protection for a domain to test owner access.
Owner sessions
A sign-in link works once, for 5 minutes. A domain owner's session ends:
- after 30 minutes without activity;
- 8 hours after they signed in, however active they are;
- straight away if the domain stops having owner access, for example when Website protection is turned off, the domain is removed or the account is closed.
The owner then sees why they were signed out, and is asked to open the site again from their hosting account. If you set a support link, it's shown there too.
Audit log
Owner sign-ins, sign-in links and owner changes appear in your audit log. Owners have no stillorigin account, so entries show how the owner signed in instead of a name, for example domain owner via API key (current), domain owner via agent 12 or domain owner (test login).
Creating sign-in links with the API
Your billing system, control panel or your own code creates a sign-in link when your customer asks to manage their site's protection, then sends their browser to it. With WHMCS, the WHMCS module does this for you, and on cPanel the cPanel plugin does. To look up a domain or turn Website protection on and off from your own billing system or CRM, see the API.
Request
POST https://control.stillorigin.app/v1/owner-logins
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY
Authorise with either:
- your account's API key. If you've created a new key and kept the old one working, the old key also works during its 7-day overlap; or
- an origin agent key. An agent key only works for domains on that agent's origin servers. On the origin server, it's in
/etc/stillorigin-agent/agent.key, readable by root only.
The body has exactly one of:
domainId: the domain's number (preferred), for example{"domainId": 2050};domain: the domain name, for example{"domain": "shop.example.com"}. Case and spaces around the name are ignored.
A name is matched exactly first, then with or without www., so www.shop.example.com finds shop.example.com and the other way round. The owner's settings cover both names.
Response
A successful request returns 200:
{
"url": "https://owners.stillorigin.app/login/sol_…",
"expiresAt": "2026-11-14T02:02:04.8858764+00:00",
"domainId": 2050
}
urlis the sign-in link. Send your customer's browser to it straight away. It works once.expiresAtis when the link stops working, in UTC, 5 minutes after it was made.domainIdis the domain the link is for.
Treat the link like a password: anyone who opens it first is signed in to that domain. Don't log it, email it or store it.
Errors
| Status | Body | Meaning |
|---|---|---|
| 400 | {"error":"invalid_request"} | Neither domainId nor domain was given, both were, or the name was empty. |
| 400 or 415 | The body isn't valid JSON, or Content-Type isn't application/json. | |
| 401 | no error code | The key is missing or not recognised, including a key for a closed account. |
| 404 | {"error":"domain_not_found"} | The domain isn't in this account, or (with an agent key) the domain isn't on that agent's origin servers. |
| 409 | {"error":"not_l7","domainId":2051} | Website protection isn't on for that domain, so it has no owner access. Hide the button for that domain. |
| 429 | {"error":"rate_limited"} | More than 120 links in a minute for one key or agent. There's no Retry-After header, so wait a little and try again. |
Example: a button in your client area
Add a Site protection button next to each Website protection domain in your client area. When your customer clicks it, your server creates the link and redirects them.
With curl:
curl -sS https://control.stillorigin.app/v1/owner-logins \
-H "Authorization: Bearer $STILLORIGIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"domainId": 2050}'
The flow on your server:
when the signed-in customer clicks "Site protection" for a domain:
check the customer owns that domain in your own system
POST https://control.stillorigin.app/v1/owner-logins
with {"domainId": the domain's stillorigin number}
and your API key, read from your server's settings
if the response is 200:
redirect the customer's browser to response.url
if 409 not_l7:
tell the customer site protection isn't available for this domain
otherwise:
show a "try again shortly" message, and log the status code (never the url)
Create the link only when your customer clicks, never ahead of time, in a page that might be cached, or in an email.
Keeping your keys safe
- Keep your API key and agent keys on your server. Never put them in browser code, a page's HTML or a mobile app.
- Check that the signed-in customer owns the domain before you create a link. stillorigin can't tell which of your customers is asking.
- Anyone with your API key can create sign-in links for any Website protection domain in your account. If a key leaks, create a new one under My account › API key (see Your API key).