Scope
Define the targets you are testing and filter history, interception and extensions by them.
Scope
Scope is the list of targets you are testing. Once defined, you can show only in-scope traffic, hold only in-scope packets, and let extensions check a target.
Scope is configured in the top-level Settings tab.
Scope entries
Each entry has:
| Field | Meaning |
|---|---|
| Host | example.com:443, 10.0.0.5:8080, a host without a port, or * for every host |
| Protocol | Any of TCP, TLS, UDP, DTLS, QUIC |
| Enabled | Untick to disable an entry without deleting it |
An entry only matches the protocols it names. example.com:443 with TLS only does not match the same host over TCP.
An empty Scope list means everything is in scope. Nothing is filtered out until you add an entry.
Adding targets from Proxy History
Right-click a row in Proxy History and choose Add to Scope. The host, port and protocol are filled in for you.
Using Scope
- Proxy History: the scope dropdown next to the search box offers Show all, In scope only and Out of scope only. It combines with whatever you typed in the search box.
- Interception rules: the Scope check holds only packets that are in scope, or only those that are not. See Interception Rules.
- Extensions: call
is_in_scope(host, protocol)to test a target. See the Extension API. - AI access: an AI agent can be limited to Replay targets in Scope. See AI Access.