01What Signals observes
Begin here when you need to know exactly what the assessment does and does not do. Stay with the domain, relationship or service state named on the page; the task does not widen silently into a different security or product claim.
02What Signals can conclude
The assessment uses direct protocol observations and passive intelligence but stops before exploitation, authentication attempts, brute force and fuzzing. Open the relevant report evidence when you need to verify the source, observation time, attribution or qualification behind it.
03What remains unknown
Complete the step shown on the page, then check the resulting state before moving on. Unknown, unavailable and not-applicable outcomes remain distinct, so absence is never presented as a successful or reassuring result.
04What requires human validation
Methodology changes interrupt trends until comparable evidence exists. Record the resulting owner, evidence or recovery state where the product provides it, so another person can verify what happened without repeating the task.