Evidence you can explain, for every domain you assess

Score a domain you do not own.

Enter a prospect's domain and TrustSek collects public evidence about it. There is nothing to install, no access to ask for and no questionnaire to wait on. The prospect is not contacted.

Where it fits in the work.

• Before a quote. Score the prospect's domain while the proposal form is still out, and see which answers to look at more closely.
• In the proposal form. Replace a generic question with a specific one: “Your domain publishes no DMARC policy. Is a fix planned?” is easier to answer honestly than “Do you protect against email spoofing?”.
• At renewal. Run the same check again and compare it with last year's result, under the same scoring policy version.
• For brokers. Check a client's domain before it goes to market, so the client can fix the obvious findings before any insurer sees them.

The score is a multiplier, not a grade.

The score says how much higher a domain's risk is than a baseline organisation's. The bands are fixed and published, and every result records the scoring policy version that produced it, so a change in method is never mistaken for a change in the risk.

See what could not be checked.

Every source ends a scan in one of four states, and only one of them means clean. A source that failed, or was never asked, is shown as exactly that, so you can see which evidence a score rests on and which it is missing.

Look across a book.

Portfolio views put many domains side by side, so you can see where risk concentrates across the accounts you are responsible for.

Bring domains in over the API.

The public API lets your own systems add companies and start their scans, with an API key. See the methodology for what each score is made of.

The score has limits, and we list them.

• The baseline and the module weights are policy, not measurement. The score ranks and explains risk; it is not a validated claims probability.
• Vulnerability detection is passive and version-based. It reads what a site advertises and cannot see a fix that was backported without a version change.
• Ransomware matching is deliberately conservative. A victim listed under a trading name we do not know may be missed.
• Findings are scored independently. The model does not yet reward risks that compound each other.

The full list is on the methodology page.

Questions

Is TrustSek an insurer or a broker?

No. TrustSek is an assessment tool. It does not sell, price or underwrite insurance, and a score is not an insurance decision.

Does the score predict claims?

No. It ranks and explains the risk visible from the outside against a fixed baseline. The baseline and weights are policy, not a validated claims model, so use the score alongside your own underwriting data.

Does it watch the domains in a book between checks?

No. A score describes the domain when the scan ran. Run the check again when you need a current reading, for example at renewal.