Burp Suite uses URL-matching rules to define the Target scope. These rules also define the scope for other features:
You can configure URL-based scoping in normal or advanced mode. Normal mode performs better in most situations. Advanced mode provides more power and flexibility where needed. The scope control rules are not case-sensitive.
Normal scope control enables you to quickly specify URL prefixes for items that are in or out of scope. You can include a specific protocol in each prefix. If you omit the protocol, the rules match both HTTP and HTTPS.
Examples of valid URL prefixes are:
http://example.com/path.
https://example.com/admin.
example.com.
example.com/myapp/.
http://example.com:8080/login.
Wildcard expressions are not supported in simple URL prefixes.
Advanced scope control uses URL-matching rules rather than simple prefixes. For a URL to match the rule, it must match all the specified features:
The easiest way to create an advanced URL-matching rule is to copy the relevant URL:
This creates a rule that matches the URL and any other addresses that have the URL as a prefix: Burp places a wildcard at the end of the file expression. To fine-tune the URL-matching, click Edit.
To load a list of items from a text file, click Load. Make sure that each item in the list is either a URL or a hostname. Burp creates a rule for each item.
Regex isn't currently supported for loading port or file information from a text file.