In short
DNSLog is an open-source tool that records DNS lookups and HTTP requests sent to domains it controls. Security testers use it to confirm blind vulnerabilities, such as blind SQL injection, because a vulnerable server looks up a unique DNSLog name. Attackers use the same callbacks to check exploits before sending real payloads.
Key takeaways
- What it is
- An out-of-band callback logger. The original BugScanTeam code is Python and Django, GPL-2.0, archived in 2021, with many clones.
- How it works
- A payload makes the target resolve a unique name under a logging domain. DNSLog's own DNS server records the lookup.
- Why it matters
- A callback shows a blind flaw is real and the server can reach the internet. It is often the first step before a real payload.
- What Odin Research saw
- 33 DNSLog endpoints in Monograph 17, mostly on Chinese clouds, with the API on port 8000 on 54.5% of them.
- What to do first
- Block direct egress from servers and route their DNS through Protective DNS that sinkholes OAST zones.
What is DNSLog?
DNSLog is an open-source tool that records DNS lookups and HTTP requests sent to domains it controls. Testers use it to confirm blind flaws, such as blind SQL injection or command injection, that return no visible answer. If the target server looks up a unique DNSLog name, the flaw is real and reachable.
The best-known code base is BugScanTeam/DNSLog on GitHub, from the Chinese security company behind the BugScan scanner. Its README describes it as a tool that monitors DNS resolution records and HTTP access records, and as a core library of the BugScan distributed scanning framework. The repository is GPL-2.0 licensed and was archived, read-only, on 22 March 2021.
The name is also used for public DNSLog-style web services and for clones that copy the same idea. Together they form part of the wider out-of-band application security testing (OAST) family, next to Interactsh and Burp Collaborator.
How DNSLog works
PortSwigger describes OAST as using external servers to see otherwise invisible vulnerabilities. DNSLog applies that idea with a DNS server the tester controls. According to the BugScanTeam README, a setup needs two domains and a public IP address:
- A name-server domain. Two NS host records point at the DNSLog server's public IP.
- A logging domain. Its NS records point at those name servers, so every lookup under it reaches DNSLog.
- Per-user subdomains. Each user gets a subdomain. Any name below it is logged with the source address and time.
- A web log. The WebLog component records HTTP requests, including path, source IP and user agent, so command output can also be passed in a URL.
The tester plants a payload that makes the target resolve a unique name, for example inside an injected SQL function or shell command. The target, or its DNS resolver, looks up the name. DNSLog records the lookup and the tester reads it from the web panel or an API.
The original project is written in Python on Django and bundles its own DNS server. Django serves the panel on port 8000 by default, and the README describes an optional Nginx front end for HTTPS on 443.
DNSLog versions, clones and public services
Because the original repository is archived, many current DNSLog servers run forks or rewrites. Odin's Monograph 17 found two route families in the wild. Panels compatible with the popular public DNSLog service expose /getdomain and /getrecords, or .php forms of those paths. BugScanTeam's code uses /api/ routes instead.
The BugScanTeam repository had about 1,400 stars and 451 forks on 21 November 2026. Most DNSLog infrastructure Odin observed sits in China and Hong Kong, while Interactsh and Burp Collaborator sit mostly on Western cloud providers.
Is DNSLog legal? Yes. Running a callback server is legal. Planting payloads in systems you are not authorized to test is not.
How attackers use DNSLog
A callback server is the quiet first step of many attacks. Before an intruder sends a real payload, a DNSLog lookup tells them a blind SQL injection, command injection or deserialization bug works, and that the target can reach the internet. The same channel can carry small amounts of data inside DNS names. MITRE ATT&CK tracks the wider abuse of DNS as Application Layer Protocol: DNS (T1071.004).
Odin has found DNSLog names inside real attacker tooling. Monograph 17 describes a confirmed workbench with DNS exfiltration scripts that used public OAST and DNSLog zones, and another open directory with Java exploit templates that called DNSLog subdomains. Monograph 09 found an exploit workbench whose debug log held 43 unique per-session OAST and DNSLog callbacks.
What Odin Research observed
- 33 endpoints, 8 likely listeners. Monograph 17 mapped 1,794 out-of-band callback endpoints. DNSLog accounted for 33 endpoints on 33 hosts. One was confirmed and seven suspected, and the other 25 stayed candidates.
- Port 8000 is the tell. DNSLog pairs a DNS listener on
53with an HTTP API. That API ran on8000on 18 of the 33 endpoints (54.5%). - Chinese clouds. Tencent (11) and an Alibaba subsidiary (9) hosted most DNSLog endpoints, with 20 in China and 6 in Hong Kong.
- Shared with offensive tools. One confirmed DNSLog host also ran a VShell WebSocket C2 listener. Another sat next to an ARL recon panel.
- A busy cloud range. On 18 November 2026, Odin first observed a DNSLog collector, a VShell listener, a CyberStrikeAI engine and a HexStrike AI tool bridge in one Alibaba Cloud range, on four separate servers. Monograph 19 saw DNSLog on
8000and8443in the same range. Nothing links the four servers, so they are treated as separate hosts.
Most DNSLog servers are ordinary testing infrastructure. The dangerous ones are those that share a host with C2 or show up inside exploit kits.
How to detect DNSLog callbacks
- Server lookups of OAST zones. A database or application server has no reason to resolve names under public DNSLog or Interactsh zones. Treat that as a sign someone is probing it.
- Random-looking labels. Alert on long, random-looking first labels in server DNS traffic. Monograph 17 suggests watching for labels of 26 to 36 characters.
- Poller files. Small scripts that hold both
/getdomainand/getrecordsURLs are DNSLog pollers. - Daemons on your own hosts. A Linux server that runs a
dnslogprocess outside sanctioned red-team machines needs an owner.
Monograph 17 publishes a Suricata rule set with signatures for callback DNS lookups and DNSLog polling. It adds Sigma rules for server OAST lookups and unapproved OAST daemons, a YARA rule for DNSLog polling files and a Microsoft Sentinel KQL hunt. All are in the Defense Kit. For the hunting method itself, see threat hunting.
How to defend against out-of-band testing
- Block direct egress. Internal servers should not send DNS, HTTP or SMTP straight to the internet. Callbacks only work if your servers can call out.
- Route server DNS through Protective DNS. Sinkhole known OAST and DNSLog zones in your forwarders. A sinkhole turns a silent probe into an alert.
- Fix the bug class. Blind callbacks point to injection and deserialization flaws. Patch and validate input, starting with public-facing applications.
- Tell your testers. Agree in advance which OAST domains your authorized testers will use, so their callbacks can be cleared quickly.
DNSLog compared with Interactsh and Burp Collaborator
| Tool | Protocols | Typical hosting in Monograph 17 | Notes |
|---|---|---|---|
| DNSLog | DNS and HTTP | Tencent and Alibaba, China and Hong Kong | Original code archived in 2021; many clones; API often on 8000 |
| Interactsh | DNS, HTTP(S), SMTP(S) and LDAP; more when self-hosted | Western cloud providers | MIT-licensed, from ProjectDiscovery, with public default servers |
| Burp Collaborator | Callbacks for Burp Suite scans | Western cloud providers | 109 private servers in Monograph 17 |
Frequently asked questions about DNSLog
What is DNSLog?
DNSLog is an open-source tool that logs DNS lookups and HTTP requests to domains it controls. Testers use it to confirm blind vulnerabilities, because a vulnerable server looks up a unique DNSLog name.
Is DNSLog malware?
No. DNSLog is a legitimate testing tool. Attackers use it too, to check whether a blind exploit works before sending a real payload, and sometimes to move small amounts of data in DNS names.
Is DNSLog legal?
Running a DNSLog server is legal. Planting payloads in systems you do not own or are not authorized to test is illegal in most countries.
Who made DNSLog?
The widely used DNSLog code base is BugScanTeam/DNSLog on GitHub, built on Python and Django as a core library of the BugScan scanner. The repository was archived in March 2021.
What is a DNSLog domain used for?
It is a logging domain whose name servers point to the DNSLog server. Each user gets a subdomain, and any lookup below it is recorded, which shows that a target reached out.
DNSLog vs Interactsh: what is the difference?
Both are OAST callback servers. DNSLog logs DNS and HTTP and is common on Chinese clouds. Interactsh, from ProjectDiscovery, also captures SMTP and LDAP and runs public default servers.
How do I detect DNSLog callbacks?
Watch for internal servers resolving OAST or DNSLog zones, long random-looking DNS labels and poller files with /getdomain and /getrecords. Odin Research publishes matching Suricata, Sigma, YARA and KQL rules.
How do I stop DNSLog callbacks?
Block direct DNS, HTTP and SMTP egress from servers, route their DNS through Protective DNS that sinkholes OAST zones, and fix the injection flaws the callbacks reveal.
Sources
- BugScanTeam, DNSLog repository, GitHub. github.com/BugScanTeam/DNSLog (checked 21 November 2026)
- PortSwigger, Out-of-band application security testing (OAST). portswigger.net/burp/application-security-testing/oast (checked 21 November 2026)
- ProjectDiscovery, Interactsh repository, GitHub. github.com/projectdiscovery/interactsh (checked 21 November 2026)
- MITRE ATT&CK, Application Layer Protocol: DNS (T1071.004). attack.mitre.org/techniques/T1071/004/ (checked 21 November 2026)
Related tools and terms
What is Interactsh?
Interactsh is ProjectDiscovery's open-source OAST server and client for catching DNS, HTTP and other callbacks.
OAST serviceWhat is Burp Collaborator?
Burp Collaborator is PortSwigger's callback service for Burp Suite, used to detect out-of-band vulnerabilities.
Offensive toolWhat is ezXSS?
ezXSS is an open-source collector for blind cross-site scripting (XSS) payloads. It records pages where a payload fires.
Interception proxyWhat is mitmproxy?
mitmproxy is an open-source interactive HTTPS proxy. It installs its own root certificate to read encrypted traffic.
Security testing suiteWhat is Yakit?
Yakit is a security testing suite with a desktop interface and a remote engine that can intercept traffic, fuzz web parameters and run exploit checks.
Reconnaissance platformWhat is ScopeSentry?
ScopeSentry is an open-source asset discovery and scanning platform that maps subdomains, ports and web services.
Odin Research
Get the rules, not just the definition
Every Odin Research report ships with verified indicators and detection rules you can load today.