Lakukan enumerasi DNS record, audit protokol keamanan email, dan deteksi kerentanan subdomain takeover.
Juga dikenal sebagai GuardBee/guardbee-mcp, @guardbee/mcp-dns-intelligence
- Stars
- 2
- Tools
- 6
- Unduhan, 30 hari
- 2.296
- Versi terbaru
- 0.2.3
- Commit terakhir
- 12 Nov 2026
- Lisensi
- MIT
Apa itu dns-intelligence MCP?
Lakukan enumerasi DNS record, audit protokol keamanan email, dan deteksi kerentanan subdomain takeover. Server ini menyediakan 6 tool, seperti enumerate_dns, audit_domains, enumerate_subdomains.
Ringkasan dibuat dari README proyek
Tentang dns-intelligence MCP server
Security researcher dan developer dapat melakukan audit DNS mendalam serta asesmen keamanan email secara langsung melalui AI client. Server ini menyediakan tools untuk mengenumerasi berbagai DNS record, termasuk A, MX, dan TXT, sambil memberikan grade AβF berdasarkan postur keamanan domain tersebut. Server ini secara khusus menargetkan autentikasi email dengan menganalisis konfigurasi SPF, DMARC, dan DKIM untuk mengidentifikasi miskonfigurasi seperti excessive lookups atau kebijakan yang hilang.
Selain lookup record standar, server ini mengidentifikasi potensi kerentanan subdomain takeover dengan memindai Certificate Transparency logs dan memeriksa adanya dangling CNAME records. Anda juga dapat melakukan probing pada selector umum untuk DKIM serta mengevaluasi integritas pengaturan DNSSEC dan CAA. Pengguna dapat menjalankan pengecekan ini secara lokal via npx atau mengintegrasikannya ke dalam workflow menggunakan MCP tools yang tersedia. Sistem ini dirancang agar ringan, menggunakan modul bawaan Node.js tanpa dependensi eksternal, dan menjaga telemetri tetap nonaktif secara default.
Apa yang bisa Anda lakukan dengannya
- 1Audit protokol keamanan emailAnalisis pengaturan SPF, DMARC, dan DKIM pada sebuah domain untuk mendapatkan rekomendasi perbaikan yang spesifik.
- 2Deteksi risiko subdomain takeoverIdentifikasi subdomain yang rentan terhadap takeover dengan memeriksa adanya dangling CNAME records.
- 3Lakukan enumerasi DNS lengkapDapatkan laporan komprehensif dari seluruh DNS record dan grade keamanan untuk domain tertentu.
- 4Bandingkan grade keamanan beberapa domainEvaluasi hingga 20 domain berbeda sekaligus untuk membandingkan temuan keamanannya.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal dns-intelligence MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal dns-intelligence MCP di Claude Code
$ claude mcp add dns-intelligence -- npx -y @guardbee/mcp-dns-intelligenceInstal dns-intelligence MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"dns-intelligence": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}Instal dns-intelligence MCP di VS Code
.vscode/mcp.json
{
"servers": {
"dns-intelligence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}Instal dns-intelligence MCP di VS Code CLI
$ code --add-mcp '{"name":"dns-intelligence","type":"stdio","command":"npx","args":["-y","@guardbee/mcp-dns-intelligence"]}'Instal dns-intelligence MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"dns-intelligence": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}Instal dns-intelligence MCP di Codex
$ codex mcp add dns-intelligence -- npx -y @guardbee/mcp-dns-intelligenceInstal dns-intelligence MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.dns-intelligence] command = "npx" args = ["-y", "@guardbee/mcp-dns-intelligence"]
Instal dns-intelligence MCP di Gemini CLI
$ gemini mcp add -s user dns-intelligence npx -- -y @guardbee/mcp-dns-intelligenceInstal dns-intelligence MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"dns-intelligence": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}Tool dns-intelligence MCP 6
Terdeteksi dari READMEenumerate_dnsaudit_domainsenumerate_subdomainscheck_takeovercheck_email_securitylookup_dns
| enumerate_dns | β | |
| audit_domains | β | |
| enumerate_subdomains | β | |
| check_takeover | β | |
| check_email_security | β | |
| lookup_dns | β |
Pengecekan otomatis
Berjalan 13 Nov 2026Laporan lengkap βLolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSTidak diperiksa
- Tools yang bersifat destruktif telah diberi labelLolos
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaLolos
README
Lihat di GitHub@guardbee/mcp-dns-intelligence
π¬π§ English | πΉπ· TΓΌrkΓ§e | π¨π³ δΈζ | π―π΅ ζ₯ζ¬θͺ | π°π· νκ΅μ΄ | π§π· PortuguΓͺs | πͺπΈ EspaΓ±ol | π©πͺ Deutsch
An MCP server that enumerates DNS records, detects SPF / DMARC / DKIM misconfigurations, and finds subdomains (Certificate Transparency + wordlist) that can be taken over. Uses Node.js's built-in dns/promises β no external dependencies.
Telemetry is off by default. With
GUARDBEE_TELEMETRY=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare replaced with a placeholder. See@guardbee/mcp-telemetry.
Features
- Full DNS Enumeration β A, AAAA, MX, NS, TXT, CNAME, SOA records
- SPF Analysis β
+all,?all, duplicate records, and the RFC 7208 limits counted the way receivers do: DNS lookups across nestedinclude/redirect(max 10), void lookups (max 2), include loops and missing includes - DMARC Analysis β policy (
none/quarantine/reject),pct, missingruaaddress - DKIM Check β probes 9 common selectors (
default,google,selector1,mail, etc.) - Subdomain Discovery β names from Certificate Transparency logs (crt.sh and Cert Spotter, queried in parallel; only the domain name is sent) plus a 75-name wordlist, with wildcard DNS filtered out; every live name is checked for subdomain takeover
- Email Security Summary β combined SPF + DMARC + DKIM analysis with copy-pasteable fix recommendations
- 23 Unit Tests β pure logic tests, no network connection required
Quick Start
npm install -g @guardbee/mcp-dns-intelligence
Add to claude_desktop_config.json:
{
"mcpServers": {
"guardbee-dns-intelligence": {
"command": "npx",
"args": ["-y", "@guardbee/mcp-dns-intelligence"]
}
}
}
MCP Tools
| Tool | Description |
|---|---|
enumerate_dns |
Full DNS check with an AβF grade: records, SPF/DMARC/DKIM, MTA-STS, DNSSEC, CAA, nameservers |
audit_domains |
Audits up to 20 domains and compares their grades and top findings |
enumerate_subdomains |
Probes common subdomains (wildcard-aware); detects subdomain takeovers |
check_takeover |
Checks given hostnames for subdomain takeover |
check_email_security |
Combined SPF + DMARC + DKIM audit with fix recommendations |
lookup_dns |
Targeted DNS lookup for a specific record type (A/MX/TXT/etc.) |
Example Usage
You can ask Claude:
"Is there a problem with example.com's DNS configuration?"
"Audit example.com's email security β SPF, DMARC, and DKIM"
"List example.com's subdomains, flag any dangling ones"
"What are example.com's MX records?"
Example Output
Email Security Check: example.com
ββββββββββββββββββββββββββββββββββββββββββββββββββ
ββ SPF βββββββββββββββββββββββββββββββββββββββββ
β v=spf1 include:_spf.google.com -all
ββ DMARC βββββββββββββββββββββββββββββββββββββββ
β No DMARC record found at _dmarc.example.com
Add: v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
ββ DKIM ββββββββββββββββββββββββββββββββββββββββ
β Found DKIM selectors: google
SPF Findings
| Code | Severity | Description |
|---|---|---|
SPF_MISSING |
π‘ Medium | No SPF record found |
SPF_PERMISSIVE_ALL |
π΄ Critical | +all β allows any server |
SPF_NEUTRAL_ALL |
π High | ?all β doesn't reject unauthorized senders |
SPF_NO_ALL |
π‘ Medium | No all mechanism |
SPF_TOO_MANY_LOOKUPS |
π High | > 10 DNS lookups β causes SPF to fail |
SPF_DUPLICATE |
π High | Multiple SPF records |
SPF_AT_LOOKUP_LIMIT |
π΅ Low | Exactly 10 lookups β one more include breaks SPF |
SPF_TOO_MANY_VOID_LOOKUPS |
π High | More than 2 includes return no record |
SPF_INCLUDE_MISSING |
π High | An include/redirect target has no SPF record (permerror) |
SPF_INCLUDE_DUPLICATE |
π High | An included domain publishes several SPF records |
SPF_INCLUDE_LOOP |
π High | Includes loop back to a record being evaluated |
SPF_PTR |
π΅ Low | Uses the deprecated ptr mechanism |
DMARC Findings
| Code | Severity | Description |
|---|---|---|
DMARC_MISSING |
π High | No DMARC record |
DMARC_NO_POLICY |
π High | Missing p= policy |
DMARC_POLICY_NONE |
π‘ Medium | p=none β monitoring mode, no enforcement |
DMARC_PCT_LOW |
π΅ Low | pct < 100 β partial enforcement |
DMARC_NO_RUA |
π΅ Low | No aggregate report address (rua) |
DMARC_MULTIPLE |
π High | Several DMARC records β receivers ignore all of them |
DMARC_INVALID_POLICY |
π High | p= is not none, quarantine or reject |
DMARC_SUBDOMAINS_NONE |
π‘ Medium | sp=none leaves subdomains spoofable |
DOMAIN_NOT_FOUND |
π High | The domain does not exist (NXDOMAIN) |
Subdomains without their own DMARC record inherit the parent domain's (sp= policy), as receivers do. Subdomain enumeration detects wildcard DNS and leaves out names answered only by the wildcard.
DKIM, MX and Transport Findings
| Code | Severity | Description |
|---|---|---|
DKIM_NOT_FOUND |
π‘ Medium | No DKIM key under ~35 common selectors (pass yours via dkimSelectors) |
DKIM_KEY_WEAK |
π High | RSA key under 1024 bits |
DKIM_KEY_1024 |
π‘ Medium | 1024-bit RSA key β rotate to 2048 (RFC 8301) |
DKIM_KEY_INVALID |
π‘ Medium | Published key cannot be parsed |
DKIM_TESTING |
π΅ Low | t=y test mode |
MX_UNRESOLVABLE |
π High | An MX host has no A/AAAA record |
MTA_STS_MISSING |
π΅ Low | No MTA-STS: inbound mail can be downgraded to plaintext |
MTA_STS_MX_MISMATCH |
π High | Enforce policy omits a live MX β compliant senders refuse to deliver |
MTA_STS_POLICY_UNREACHABLE / _INVALID |
π‘ Medium | Policy file missing, redirected or malformed β senders ignore MTA-STS |
MTA_STS_TESTING / _MODE_NONE / _MAX_AGE_SHORT |
π΅ Low | Not enforcing, withdrawn, or max_age under a day |
TLSRPT_MISSING / _INVALID |
π΅ Low | No usable TLS-RPT next to MTA-STS |
SPF_MISSING is π High when the domain has MX records (with a starting record, e.g. v=spf1 include:_spf.google.com ~all for Google Workspace) and π‘ Medium otherwise (suggests v=spf1 -all).
Nameserver Findings
Each nameserver of a zone is queried directly over DNS (UDP/TCP 53): an SOA query without recursion, an AXFR request (only the first messages are read β the zone is never downloaded), and a recursive query for a name it does not host. Skip with --no-ns-probe / nameserverProbe: false.
| Code | Severity | Description |
|---|---|---|
NS_AXFR_ALLOWED |
π High | Anyone can download the whole zone (zone transfer) |
NS_LAME |
π High | A listed nameserver does not answer authoritatively (REFUSED, SERVFAIL, no AA, or no answer) |
NS_UNRESOLVABLE |
π High | A nameserver's own name has no address |
NS_OPEN_RESOLVER |
π‘ Medium | The nameserver answers recursive queries for anyone (amplification, cache poisoning) |
NS_SOA_SERIAL_MISMATCH |
π΅ Low | Servers of the same primary return different serials (multi-provider setups are compared per primary) |
DNSSEC and CAA Findings
| Code | Severity | Description |
|---|---|---|
DNSSEC_BROKEN |
π΄ Critical | Validation fails β validating resolvers (Google, Cloudflare, most ISPs) cannot resolve the domain |
DNSSEC_NO_DS |
π‘ Medium | Zone is signed but the parent has no DS, so nothing is validated |
DNSSEC_WEAK_ALGORITHM |
π‘ Medium | Deprecated signing algorithm (RSASHA1, RSAMD5, DSA, GOST; RFC 8624) |
DNSSEC_DS_SHA1 |
π΅ Low | The only DS digest is SHA-1 |
DNSSEC_DISABLED |
π΅ Low | Zone is not signed |
CAA_BLOCKS_CURRENT_CA |
π‘ Medium | CAA does not allow the CA that issued the live certificate β its renewal will fail |
CAA_UNKNOWN_CRITICAL |
π High | A critical CAA tag CAs do not understand β every CA must refuse |
CAA_MISSING |
π΅ Low | No CAA anywhere up the tree: any CA may issue |
DNSSEC is read through DNS-over-HTTPS (dns.google), comparing a validating query with a cd=1 (checking disabled) one, because Node's resolver cannot see DS/DNSKEY records or the AD flag. CAA follows RFC 8659 (nearest ancestor), and the issuer of the certificate served on :443 is compared against it. Both checks are skipped with http: false.
Subdomain Takeover Detection
Each live subdomain with a CNAME is checked, following the CNAME chain (up to 5 hops). The wildcard record is checked too: a dangling *.domain makes every unlisted name claimable.
| Risk | When | Providers |
|---|---|---|
| β οΈ takeover possible | The provider lets anyone claim the name | AWS S3 (NoSuchBucket page), Microsoft Azure and AWS Elastic Beanstalk (CNAME target NXDOMAIN), Surge.sh (project not found), and any CNAME into a domain that is not registered |
| β οΈ verify manually | The resource is gone, but the provider can require domain verification | GitHub Pages, Heroku, Netlify, Vercel, Ghost, Pantheon, WordPress.com, Help Scout, Tumblr, ngrok |
| π§Ή stale | The target is gone but sits under a registered domain only its owner controls β delete the record; not a takeover, does not fail CI | any other provider |
Each page fingerprint was checked against a random unclaimed name on the provider. Providers whose "not found" page no longer carries a stable marker are not listed. HTTP checks send one GET / to the subdomain (HTTPS, then HTTP); turn them off with --no-http / httpProbe: false. Use check_takeover / takeover <hostβ¦> for hostnames you already know.
CLI β CI/CD Integration
In addition to MCP server mode, this can also be used directly as a CLI:
# Full DNS + email security check
npx @guardbee/mcp-dns-intelligence check example.com
# Fail only on high and above
npx @guardbee/mcp-dns-intelligence check example.com --fail-on=high
# Subdomain scan β exits 1 if a dangling CNAME is found
npx @guardbee/mcp-dns-intelligence subdomains example.com
# Subdomain scan with higher concurrency
npx @guardbee/mcp-dns-intelligence subdomains example.com --concurrency=50
# JSON output
npx @guardbee/mcp-dns-intelligence check example.com --format=json
# Several domains with an AβF grade each and a summary table (or every domain in guardbee.yml when none is given)
npx @guardbee/mcp-dns-intelligence check example.com example.de example.co.uk
npx @guardbee/mcp-dns-intelligence check --format=sarif > dns.sarif
Grades: each finding deducts points (critical 40, high 20, medium 8, low 2) and the worst finding caps the grade β any critical is F, any high at most C, any medium at most B.
Exit codes: 0 = no issues Β· 1 = findings above threshold / dangling subdomain Β· 2 = error
Configuration via guardbee.yml
Create a guardbee.yml at your project root to persist CLI flags. CLI flags always override file settings.
dns-intelligence:
fail-on: high # critical | high | medium | low
concurrency: 20 # parallel subdomain probes
domains: # used when no domain is given on the CLI
- example.com
- staging.example.com
See guardbee.example.yml for a sample file.
GitHub Actions β DNS Security Audit
name: DNS Security Check
on:
schedule:
- cron: "0 6 * * *" # Every day at 06:00
workflow_dispatch:
jobs:
dns-check:
runs-on: ubuntu-latest
steps:
- name: Check DNS configuration
run: npx @guardbee/mcp-dns-intelligence check ${{ vars.DOMAIN }} --fail-on=high
- name: Scan for dangling subdomains
run: npx @guardbee/mcp-dns-intelligence subdomains ${{ vars.DOMAIN }}
GitLab CI
dns-security:
image: node:20
script:
- npx @guardbee/mcp-dns-intelligence check $DOMAIN --fail-on=high
- npx @guardbee/mcp-dns-intelligence subdomains $DOMAIN
only:
- schedules
Pre-Deployment Email Security Check
- name: Verify email security records
run: |
npx @guardbee/mcp-dns-intelligence check ${{ vars.DOMAIN }} \
--fail-on=high \
--format=json | tee dns-report.json
- name: Upload DNS report
uses: actions/upload-artifact@v4
with:
name: dns-security-report
path: dns-report.json
Development
npm install
npm test # 23 unit tests
npm run build # TypeScript compile
License
MIT β GuardBee
Feedback
Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a β on the repository helps others find it.
Pertanyaan tentang dns-intelligence MCP
Bagaimana cara menambahkan dns-intelligence MCP ke Claude Code?
Jalankan claude mcp add dns-intelligence -- npx -y @guardbee/mcp-dns-intelligence di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan dns-intelligence MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan dns-intelligence MCP?
Server ini menyediakan 6 tool, termasuk enumerate_dns, audit_domains, enumerate_subdomains, check_takeover, check_email_security.
DNS record apa saja yang bisa dienumerasi?
Server ini mendukung enumerasi lengkap untuk record A, AAAA, MX, NS, TXT, CNAME, dan SOA.
Bagaimana cara tool ini mendeteksi subdomain takeover?
Tool ini melakukan probing pada subdomain umum menggunakan Certificate Transparency logs dan wordlist, lalu memeriksa target CNAME yang aktif untuk mencari dangling resources yang bisa diklaim.
Apakah server mengirimkan data telemetri?
Telemetri dinonaktifkan secara default; Anda dapat mengaktifkannya menggunakan environment variable GUARDBEE_TELEMETRY=1.
Bisakah saya melakukan audit keamanan email secara spesifik?
Ya, server menyediakan tool untuk melakukan audit gabungan SPF, DMARC, dan DKIM lengkap dengan rekomendasi perbaikannya.