Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Offensive and testing tools

What Is Burp Collaborator? How Out-of-Band Testing Works

The callback service behind Burp Suite's blind-bug checks: how it works, why attackers like the same trick, and how to catch callbacks leaving your servers.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
OAST service

In short

Burp Collaborator is a PortSwigger network service that Burp Suite uses to find blind vulnerabilities. Burp plants a unique Collaborator subdomain in a test request. If the target server later looks up or contacts that address, Burp sees the interaction and reports the flaw. Teams can use PortSwigger's public server or run their own.

Key takeaways

What it is
PortSwigger's out-of-band testing (OAST) service for Burp Suite Professional and Burp Suite DAST.
How it works
Burp embeds a unique subdomain in a request, the vulnerable target looks it up or fetches it, and Burp polls the Collaborator server for that interaction.
Why it matters
Attackers use the same callback trick to confirm blind SSRF and SQL injection, often on private callback domains that avoid blocklists.
What Odin Research saw
516 private Collaborator endpoints on 319 IPs, 109 confirmed or suspected, mostly on Amazon and DigitalOcean. None shared a host with C2 tools.
What to do first
Stop servers from calling the internet directly, route their DNS through Protective DNS, and allowlist your own testers.

What is Burp Collaborator?

Burp Collaborator is a network service from PortSwigger that helps Burp Suite find "invisible" vulnerabilities. These flaws show no error, no change in output and no delay. Burp plants a unique Collaborator address in a test request. If the target later contacts that address, the vulnerability is confirmed.

This approach is called Out-of-band Application Security Testing, or OAST. PortSwigger says Collaborator is used in Burp Suite Professional and Burp Suite DAST. Burp Scanner uses it inside its scan checks, and testers can also use it by hand in Burp Suite Professional.

Burp Collaborator is a legitimate testing service. It matters to defenders for two reasons. Attackers use the same out-of-band trick to confirm blind bugs in your servers, and a callback to a Collaborator domain from a production server means someone is probing it.

How Burp Collaborator works

PortSwigger describes a simple loop:

  1. Burp builds a payload. Each payload is a unique subdomain of the Collaborator server's domain.
  2. Burp sends it to the target. The payload goes into a header, parameter or body field of a test request.
  3. The target may call out. If the application is vulnerable, it looks up the payload in DNS and may then send an HTTP request to it.
  4. Burp polls the server. Burp asks the Collaborator server whether any interaction arrived for that payload, and reports the issue if one did.

PortSwigger lists four main uses: detecting external service interaction, out-of-band resource loads, blind SQL injection and blind cross-site scripting. Deferred interactions also catch stored flaws, such as a payload that fires only when an administrator later views it.

Because each payload is unique, every callback maps back to exactly one probe. That is what makes the technique reliable for testers and attackers alike.

Public and private Burp Collaborator servers

By default, Burp uses a public, shared Collaborator server run by PortSwigger. Burp's settings page says the domains in use are *.burpcollaborator.net and *.oastify.com, reached on ports 80 and 443. PortSwigger adds new public domains from time to time to reduce the chance of web application firewall blocking.

Teams can also run a private Collaborator server on their own domain. PortSwigger says no license key is needed for this, because the server ships in the Burp Suite Professional executable. By default a private server listens on DNS (UDP 53), HTTP (80), HTTPS (443), SMTP (25 and 587) and SMTPS (465). It must be authoritative for its domain through DNS delegation, and its settings live in a JSON configuration file with fields such as serverDomain, eventCapture and polling.

PortSwigger advises limiting inbound access to the applications under test and their DNS servers, and running the service as a non-root user where possible.

How attackers use Burp Collaborator

Out-of-band callbacks are not unique to testers. A blind server-side request forgery or blind SQL injection runs quietly in the back end. A callback is the easiest way for anyone to confirm it.

  • Confirming blind bugs. A probe with a Collaborator payload tells an attacker that a server can be reached and can reach the internet.
  • Avoiding blocklists. Public callback zones are well known, and many Protective DNS services sinkhole them. Running a private Collaborator on a fresh domain avoids those blocks.
  • Feeding exploit templates. Exploit code and scanner templates often embed a callback name so the operator learns which targets answered.

This links to Exploit Public-Facing Application (T1190). A callback shows reach, not a successful exploit.

What Odin Research observed

Odin Research mapped private Collaborator servers in Monograph 17, a study of out-of-band callback infrastructure. Standalone listeners stay withheld because most belong to testers.

  • 516 endpoints on 319 IP addresses. Of these, 62 were confirmed and 45 suspected Collaborator servers, plus 2 on dynamic lines. The other 407 were candidates.
  • Western clouds. Amazon (142) and DigitalOcean (108) hosted the most. The United States (180) and Germany (84) led by country.
  • Mail ports as well as web. The most common ports were 443 (213), 80 (199), 465 (34) and 587 (27). Of 259 TLS nodes, 236 (91.1%) shared one Java TLS fingerprint.
  • No C2 neighbours. Several standalone servers used custom certificate domains, and one hub listened on 18 ports. None showed co-hosted C2 tooling. One server carried an identifiable testing firm's certificate.
  • In attacker files. On one confirmed offensive workbench, a Java memory-shell template called an oastify name. Public scanner templates mirrored on other hosts used *.burpcollaborator.net.
  • Lookalikes removed. 356 AWS load-balancer endpoints echoed headers and only looked like callback servers. Odin left them out of every count.

The lesson: a Collaborator server alone says nothing about intent. A callback from your own production server says a lot.

How to detect Burp Collaborator callbacks

  • DNS from servers. Alert when a web, middleware or database server resolves a long random label under burpcollaborator.net or oastify.com.
  • The server header. Collaborator answers with a BurpCollaboratorServer server header, which helps you spot private servers in proxy logs.
  • Odd egress. Servers that start DNS, HTTP or SMTP sessions to new domains right after a strange inbound request are worth a look.
  • Your own testers. Register approved scanner IPs and private Collaborator domains before each test window, so real alerts stand out.

Monograph 17 publishes Suricata signatures for the Collaborator server header and for long labels under the Collaborator zones, a Sigma rule for unapproved callback daemons, and a YARA rule for Collaborator server configuration files. They are in the Defense Kit.

How to defend against out-of-band testing abuse

  1. Cut server egress. Block direct outbound DNS, HTTP, HTTPS and SMTP from web, middleware and database subnets, except to explicit allowlists.
  2. Route server DNS through Protective DNS. Sinkhole public OAST zones for servers that have no testing role.
  3. Fix the bug, not the callback. A callback means the input reached a sink. Patch the vulnerable code path and review the misconfigurations that let it reach the internet.
  4. Allowlist sanctioned tests. Keep a versioned list of scanner IPs and private callback domains for each test window.

Burp Collaborator compared with other OAST services

ServiceMakerEndpoints in Monograph 17Where it runs
Burp CollaboratorPortSwigger516 (109 confirmed or suspected)Mostly Amazon and DigitalOcean, US and Germany
InteractshProjectDiscovery1,245 (638 confirmed or suspected)Mostly Amazon and DigitalOcean, US and Germany
DNSLogBugScanTeam and other open-source projects33 (8 confirmed or suspected)Mostly Tencent and Alibaba, China and Hong Kong

Blind XSS callbacks have their own tools as well, such as ezXSS.

Frequently asked questions about Burp Collaborator

What is Burp Collaborator?

Burp Collaborator is a PortSwigger network service that lets Burp Suite detect blind vulnerabilities by watching for DNS and HTTP interactions with unique payload subdomains.

Is Burp Collaborator malicious?

No. It is a legitimate testing service. Attackers can use the same out-of-band technique, so a Collaborator callback from a production server deserves investigation.

What domains does Burp Collaborator use?

PortSwigger's public server uses *.burpcollaborator.net and *.oastify.com on ports 80 and 443, and PortSwigger adds new public domains from time to time.

Is Burp Collaborator free?

Collaborator features are part of Burp Suite Professional and Burp Suite DAST. PortSwigger says you do not need a license key to run your own private Collaborator server.

How do I set up a private Burp Collaborator server?

Run the server from the Burp Suite Professional executable on a host you control, delegate a domain to it, open its DNS, HTTP, HTTPS and SMTP ports, and set fields such as serverDomain in its configuration file.

What vulnerabilities does Burp Collaborator find?

PortSwigger lists external service interaction, out-of-band resource loads, blind SQL injection and blind cross-site scripting, including stored flaws that fire later.

How do I detect Burp Collaborator traffic?

Watch for servers resolving long random labels under burpcollaborator.net or oastify.com, and for the BurpCollaboratorServer header. Odin Research publishes Suricata, Sigma and YARA rules for this in its Defense Kit.

Burp Collaborator vs Interactsh: what is the difference?

Both are OAST callback services. Burp Collaborator is PortSwigger's service built into Burp Suite, while Interactsh is an open-source server and client from ProjectDiscovery. Odin Research saw more self-hosted Interactsh servers than Collaborator servers.

Sources

  1. PortSwigger, Burp Collaborator documentation. portswigger.net/burp/documentation/collaborator (checked 21 November 2026)
  2. PortSwigger, Deploying a private Burp Collaborator server. portswigger.net/burp/documentation/collaborator/deploying (checked 21 November 2026)
  3. PortSwigger, Burp Collaborator project settings. portswigger.net/burp/documentation/desktop/settings/project/collaborator (checked 21 November 2026)
  4. PortSwigger, Typical uses for Burp Collaborator. portswigger.net/burp/documentation/collaborator/uses (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit