A DNS & HTTP log server for verifying SSRF/XXE/RFI/RCE vulnerabilities
English Doc | 中文文档
⚠️ Release Candidate — This version is an RC. Automated E2E suites have passed against a production deployment, but it has not yet undergone manual testing by humans. Use with caution in production; expect possible issues that automated tests did not cover.
⛔ Not compatible with 1.x — GODNSLOG 2.0 is a ground-up rewrite: the database schema, configuration flags, and HTTP/DNS API are all new. Do not reuse a 1.x database or expect 1.x integrations to work; start with a fresh database and re-apply your configuration when upgrading from 1.x.
GODNSLOG 2.0 is a complete rewrite with enterprise-grade features:
- OAST Evidence Platform: Full evidence chain with Case/Payload/Interaction tracking
- Agent-Native MCP Server: AI/LLM integration with minimal permissions
- Scanner Hub: Nuclei, Burp Suite, ZAP, Yakit/Yak, xray/rad integration
- Workflow Automation: Rule-based notification triggers via Webhook/Enterprise WeChat/Feishu/DingTalk
- Canary Tokens: Long-term monitoring with multiple token types
- Rebinding Lab: Multi-stage DNS rebinding with session tracking
- Multi-Protocol Listeners: DNS, HTTP, SMTP, LDAP, SMB, FTP
- Enterprise Features: Multi-workspace, data retention, audit logging
docker build -t "user/godnslog" .
docker run -p 8080:8080 -p 53:53/udp "user/godnslog" serve -domain example.com -4 127.0.0.1For Chinese users:
docker build -t "user/godnslog" -f DockerfileCN .
docker run -p 8080:8080 -p 53:53/udp "user/godnslog" serve -domain example.com -4 127.0.0.1Frontend (Next.js):
cd frontend-next
npm install
npm run buildBackend (Go):
go build- Register your domain (e.g.,
example.com) - Set your DNS server to point to your host (e.g.,
ns.example.com→100.100.100.100) - Some registrars require NS hosts to point to different IPs initially
- Access http://your-server-ip
- Username:
admin - Password: Shown in console logs on first run
- Change password using:
go run . resetpw
- DNS/HTTP interaction capture
- Evidence timeline with scoring
- Case-based workflow
- Payload template system (30+ templates)
- Interaction clustering and noise reduction
- Nuclei templates with JSONL output
- Burp Suite extension
- ZAP script
- Yakit/Yak script
- xray/rad integration
- CI/CD gate examples
- MCP Server (Streamable HTTP)
- Agent-specific API keys with scopes
- Audit logging for agent operations
- AI evidence summarization
- Canary tokens (DNS/HTTP/SMTP)
- DNS Rebinding Lab
- Multi-protocol listeners (SMTP/LDAP/SMB/FTP)
- Webhook notifications
- Enterprise IM (WeChat/Feishu/DingTalk)
- Multi-workspace isolation
- User and role management
- Data retention policies
- Audit logging
- API key management
# Backend tests
go test ./...
# Frontend local E2E tests (mock API, requires local dev server)
cd frontend-next
npm install
npm run test:e2e
# Production E2E tests (real deployed site; credentials from env only)
cd frontend-next
ADMIN_PASSWORD=<prod admin password> npm run test:e2e:prod# View help
go run ./cmd/cli --help
# Create OAST probe
go run ./cmd/cli create-oast-probe --title "SSRF Test" --template "ssrf-basic"Open source, continuing under the original license.
