Findings & Severity
How Teste.no reports issues, tracks severity, and helps you prioritize.
What is a Finding?
A finding is a specific problem discovered by a test. Each finding has a unique fingerprint — if the same issue is found again on the next scan, it updates the existing finding rather than creating a duplicate.
Severity Levels
Security vulnerabilities, revenue impact, or availability issues. Examples: expired SSL, sensitive file exposed, broken checkout, site unreachable.
Degrades quality or user experience. Examples: missing security headers, slow response, accessibility violations.
Improvements and best practices. Examples: missing meta descriptions, HTTP/2 not enabled, minor SEO suggestions.
Dynamic Severity Escalation
Findings automatically escalate when they persist without being fixed:
| Escalation | After N recurrences | After N days open |
|---|---|---|
| INFO → WARNING | 25+ recurrences | 30+ days |
| WARNING → CRITICAL | 15+ recurrences | 14+ days |
Thresholds are configurable at two levels:
- Team-level — Settings → Team Config → Findings (base defaults)
- Per-target — Target → Settings → General → Escalation Policy (overrides team)
Finding Status Lifecycle
Muting Findings
Mute findings you don't want to act on (with optional expiry):
| Scope | Effect |
|---|---|
| By fingerprint | Mute this specific issue type everywhere |
| By test | Mute all findings from a specific test plugin |
| By test + target | Mute a test's findings on one site only |
Muted findings don't affect target status or trigger notifications.
AI Enrichment
When enabled, each finding is automatically enriched with:
AI results are cached globally — identical issue types across different sites reuse the same recommendations without redundant API calls.
Evidence
Each finding includes structured evidence showing exactly what was detected:
- Affected URLs — Clickable links to the specific pages with issues
- Metrics — Response times, scores, counts, thresholds
- Technical details — Headers, status codes, element selectors