Continuous stabilization

Continuous stabilization is what you turn on for a domain, and what your subscription pays for. Once it is on, Domain Stabilizer measures the domain continuously, fixes its initial state, protects every improvement that holds, tells you when something protected is lost, and proposes the next improvement.

This screen is where you follow that work. Open a domain and, in its menu, choose Continuous stabilization.

Anyone who can see the domain can open the screen. Turning continuous stabilization on or off is a decision about the plan: the Owner can always do it; other roles, only if their role includes billing.

• Know in one line whether the domain is fine. The block Status says it: regressions open, improvements being verified, or everything protected.
• Know what to do next. The block Now gives you one action at a time: first recover what was lost, then the improvement worth most.
• Keep what you gain. An improvement that holds becomes the new reference. If the domain later falls below it, you are told.
• Find out without checking by hand. The domain is measured on its own, and a regression reaches you by email.
• Have the story ready for your client. Every protected improvement, every regression and how it ended is kept with its date.

• Six modules are measured, each at its own pace. Email, SSL, DNS, MX, Blacklist and Uptime. How often each one is measured is set by the service and depends on the state of the module: one with something in progress (its initial state being measured, an improvement being verified, an open regression) follows a different pace from a stable one.
• First, the initial state is fixed. The first measurement is scheduled the moment you turn continuous stabilization on. For a period, each module is observed and the worst seen is kept: the lowest score, the worst risk level and every finding that showed up. When that period is over, at the next measurement of the module, that becomes its initial state and it is protected. The screen calls it the starting point. Each module fixes its own.
• The findings of the initial state do not raise alerts. They are what the domain already had.
• An improvement becomes protected when it holds. Three things count as an improvement: a known finding that is no longer there, a score that rises by at least a minimum margin, and a risk level that drops. When one is first seen, it is marked as being verified. It is checked again in every measurement and, if it holds for the whole period, it becomes protected: it is the new reference for that module.
• An improvement that does not hold is dropped. If it disappears while it is being verified, the verification ends and what was protected stays as it was. It is not a regression.
• What is protected does not go down on its own. Only you can lower it, by accepting a change as intentional.
• A regression is something protected that was lost. A finding that was not in what is protected, a score that drops, or a risk level that gets worse. A certificate that is about to expire also opens an alert. Some findings are confirmed with a second measurement before the alert is raised, so that one failed reading is not reported as a problem.
• A regression ends in one of two ways. You fix it, and when a later measurement no longer sees it the alert closes on its own as recovered. Or you accept it as an intentional change, with a reason.
• An improvement somewhere else does not close a regression. Each alert is measured against what was lost.
• Accepting a change lowers what is protected, only in that value. The alert closes, the current value becomes what is protected, and the system stops alerting about it. Who accepted it, when and why is recorded and shown in Radar.
• Stopping frees the domain in your plan. A plan reserves a number of domains; each domain with continuous stabilization turned on uses one. When you stop it, the domain is no longer measured, no more emails are sent about it, and the domain it used in your plan becomes free. The last measurement and the history are kept. The alerts that were open stay as they were: nobody measures any more, so nothing confirms whether they were solved.
• Turning it on again starts over. A new initial state is fixed from whatever the domain has that day. The history of the earlier periods is still in History.

The emails. The emails about the domain go to the billing email of the account; if the account has none, to the email of the person who created it.

• Initial state. Once, with the first measurement that gives the domain a score: how the domain is and where to start.
• Protection active. Once, when the initial state has been fixed: from then on, what gets worse is reported.
• Improvement protected. When improvements become protected. Several made together arrive in one email.
• Reminder of a proposed improvement. When there is a proposed improvement, no regression open, and the domain has gone some time without progress. A second and last one follows if nothing changes. Any progress starts the count again.
• Regression. When a measurement opens new alerts, with what changed.
• Change in an open regression. When a regression you were told about changes into a different finding.
• Recovered. When a regression you were told about is closed by a measurement.
• Change accepted. When someone accepts a change as intentional. This one goes to every Owner of the account, with the reason and who accepted it.

The screen has a title with the name of the domain. What comes below depends on whether continuous stabilization is on.

When it is off

• A notice saying that the domain is not under continuous stabilization. If it was before, the notice gives the date of the last measurement and the date it stopped, and the button View the Dashboard.
• The six modules. Under The last measurement, the score of each module the last time it was measured, with its date. If the domain was never under continuous stabilization, the block is titled What you will see here and the boxes are empty.
• The block to turn it on, with the button Turn on continuous stabilization. If the domain is not verified, the button is replaced by a notice with Verify domain.

When it is on

Next to the title there is the mark Continuous stabilization active.

• Status. One sentence with what matters most: the number of open regressions, the improvements being verified, the initial state still being measured, or how many modules are protected. Below it, the dates of the last and the next measurement, and the rule of the service with the time an improvement has to hold.
• Now. One action. With an open regression, the regression and how to recover it. Without one, the improvement worth most, with the value to copy if there is one and the button See the step-by-step. If there is nothing to do, it says so.
• The six module cards. Each one draws the score of the module over time: each dot is a measurement and the dashed line is what is protected. Uptime draws its response time instead. Under each card, its phase: Not measured, the starting point, verifying, Protected or Regression. A card with no chart says why: Waiting for the first measurement or Measured, no score. Clicking a card opens that module.
• The two views: Stabilization and Radar. The blocks above stay the same in both.

The view Stabilization answers "what do I do". It is the one that opens by default.

• A summary tab and one tab per module, with the full detail of the latest measurement.
• At the top of each module tab, a box with its state: what is protected and since when, how many known findings do not raise alerts, what is listed under Being verified, and Open regressions in this module.
• Each open regression is a card: what was protected and what there is now, the steps to get it back with the values to copy, and the dates. On the card there are two icons, Mark as acknowledged and Check again now, and below it the button It is intentional when the change can be accepted.

The view Radar answers "what happened". It has no actions.

• Under What happened, a list by date: initial state protected, improvement detected, improvement protected, improvement that did not hold, regression, recovered, broke again, change accepted with its author and reason, and the movements of the score of each module.
• A regression that has not been recovered carries the mark Still open and a button that takes you to its module in Stabilization.

The screen refreshes on its own.

Two things about continuous stabilization are in Dashboard, not here: the button that stops it, and the switch Publish the monthly report in the portal.

• Billing
• Verify domain
• Domain dashboard
• Domain history
• Timeline
• Domains
• Team