Probes overview
A probe is a saved protocol interaction belonging to a project. It stores the target host, the sequence of commands or the request body, and optional assertions. Probes can be sent standalone or assembled into chains.
Probe types
Section titled “Probe types”| Probe | Protocol | What it does |
|---|---|---|
| HTTP | HTTP/HTTPS | Send HTTP requests and inspect responses |
| SMTP | SMTP/SMTPS/STARTTLS | Send raw SMTP command sequences |
| IMAP | IMAP/IMAPS | Interact with a mailbox |
| LDAP | LDAP/LDAPS | Perform directory operations |
| SpamAssassin | spamd | Submit messages for spam scoring |
History
Section titled “History”Every time you send a probe, VirtuProbe records the result as a history entry. Each entry stores:
- The probe configuration as it was sent (with resolved
{{variable}}values) - The full response
- A timestamp
History is scoped to the individual probe. Use the History panel inside the probe editor to browse past results.
[SCREENSHOT: Probe history panel with several entries, newest at top]
Assertions
Section titled “Assertions”Most probe types support assertions — expected values checked against the response. When an assertion fails, the history entry is marked as failed.
See the individual probe pages for the assertions available per protocol.
Variable substitution
Section titled “Variable substitution”All probe types support {{variable}} placeholders in host, commands, and body fields. Variables are resolved from the active environment at send time. The stored history entry always contains the resolved values, not the template.