Burp Collaborator client

  • Last updated: January 27, 2023

  • Read time: 2 Minutes

The Burp Collaborator client enables you to make use of Burp Collaborator during manual testing.

The client generates Collaborator payloads, which are subdomains of the Collaborator server's domain. You can then pass these payloads to the application in a request to see if the application tries to interact with the Collaborator.

The client displays the results of any relevant interactions in a table. These results are retained if you close and reopen the client, and can be saved as part of a project file. The client also displays any interactions that were received while it was closed.

The client polls Burp Collaborator for results every 60 seconds. You can also poll manually by clicking the Poll now button.


We periodically add new domain names for the public Collaborator server to reduce the chance of WAF blacklisting resulting in false negatives. By default, the Burp Collaborator client always uses the newest public Collaborator domain that was available when your current version of Burp Suite Professional was released. At the moment, this will either be * or *

To ensure that you experience the full benefits of Burp Collaborator, please make sure that the machine running the Burp Collaborator client can access both of these domains on ports 80 and 443.

You can open multiple client tabs if required, enabling you to track interactions from multiple payloads in separate tables. Please note that all open tabs share the same polling schedule, so that the load on the Collaborator server does not increase as more tabs are opened.

Each instance of the Collaborator client uses the Collaborator server configuration that was in place at the time the window was opened. If you modify your Collaborator server settings (for example, to use a different private Collaborator server) then you will need to open a new client window to use that configuration.

Related pages

Was this article helpful?