Static analysis

The static analysis measures a domain once, at the moment you press the button, and shows you the result: an overall score, a score per module, the findings of each module and the actions it proposes. To open it, choose a domain and, in its menu, press Static Analysis.

It is free and does not need a subscription. It only reads public information about the domain: it does not change your DNS or your mail setup. You do not need to verify the domain to run it.

The account Owner can always see the result and run the analysis. A Operator or a Viewer sees the result if their role includes viewing domains and the Workspace is assigned to them, and runs the analysis if their role includes operating domains.

• Know where a domain stands today. One number for the whole domain and one per module, with the reason behind them.
• Know what to fix first. The analysis puts up to three findings at the top and tells you how much each one weighs and how much work it is.
• Get the exact value to publish. When the fix is a DNS record, the detail of the module gives you the host, the type and the value, ready to copy.
• Check that a fix worked. You fix, you run the analysis again, and the screen compares the new score with the one of your first analysis.

• It measures once. The result is a snapshot of that moment. Nothing is measured again until you press the button. This is the difference with Continuous stabilization: that one measures the domain continuously and protects what you achieved; this one tells you how the domain is right now.
• It checks six modules: Spam (email authentication and deliverability), SSL (certificate and HTTPS), DNS, MX (mail routing), Blacklist and Uptime (whether the site answers).
• The score goes from 0 to 100. Higher is better. Green is 80 or more, amber is 50 to 79, red is below 50. The colour rule is the same for the overall score and for each module.
• The overall score only counts the modules that could be assessed. A module with no score stays out of it, and the screen tells you which one and why.
• A module with no score is not a bad module. It means the analysis did not measure it, so it does not say it is fine and it does not say it is wrong.
• Only the latest result is kept on this screen. A new analysis replaces the previous one. The score of your first analysis is also kept, to compare. Each analysis that is saved is recorded in Timeline.
• There is a waiting time between two analyses of the same domain. While it lasts, the button is disabled and shows the time left. The saved result stays on screen.
• There is a limit of analyses per minute, shared by everyone in the account.
• There is nothing to download or share on this screen. Reports and client links are generated from the dashboard of the domain or of the Workspace: see Domain dashboard and Workspace dashboard.

From top to bottom.

The header

• The title, with the help button, and a line saying what the analysis is for.

The action panel

• The Run static analysis button. While the analysis runs it reads Analyzing…. During the waiting time it shows a countdown.
• The Free mark.
• The date and time of the snapshot on screen, once there is one.
• Included checks: the six checks the analysis covers.

Before the first analysis, the block What this free analysis shows tells you what you will get. After it, two blocks take its place.

Global summary

• From the second analysis on, a coloured line compares the score of your first analysis with the latest one: green if it went up, red if it went down, amber if it is the same.
• When not all the modules could be assessed, a line says how many were, and names each one left out with its reason.
• A line explains how the overall number is built from the modules.
• The overall score in a circle, out of 100, with its level next to it (low risk, medium risk or high risk) and one sentence that sums up the state of the domain.
• Marks with the areas affected, and up to three marks with the main findings. A red mark is a defect; a grey one is not.
• Why your score looks like this: Weakest module, with its score, and Solid modules, the ones at 90 or more.
• Fix these first: up to three findings, numbered. Each shows the module it belongs to, a mark for its impact (High impact, Medium impact or Low impact), a mark for the work it takes (Quick, Moderate or Requires planning) and, in green, the points that module would recover once it is fixed.
• More improvements: the rest of what can be improved, without a number.
• An estimated overall score: what the domain would reach if you solve the priorities. It assumes a domain with an active website and mail; on a parked or forwarding-only domain, some improvements may not apply. It is not shown when it cannot be estimated.
• A sentence that explains the diagnosis, and Next step.

Results by module

Six cards, one per module. Each one shows:

• The name of the module and its score, in the colour of the score.
• A mark with its level. If the module has no score, the mark is grey and says why it was not assessed. If the module could not be analysed, the mark reads Module error.
• Up to three findings. The dot in front of them is red when the level of the module is high, amber when it is medium and grey otherwise. With nothing to report, the card reads No standout findings in this module.
• In Spam and SSL, a few marks with measured facts, such as the days left on the certificate.
• A link at the bottom of the card, which opens the detail of the module in a dialog.

The detail of a module

• The module, the domain and the score at the top, with the Close button.
• What was measured, with the values found.
• The findings, grouped and in this order: Visible risks, Improvements, Observability improvements, Coverage and analysis limitations, Observations (no action needed). Only the groups with something in them appear.
• Recommended actions, in the modules that propose a change. Each action has a title and an explanation. When the action is a DNS record, it also shows the host, the type and the value, with the buttons Copy host, Copy type and Copy value.

• Continuous stabilization
• Domain dashboard
• Timeline
• Verify domain
• Workspace dashboard