DNS 레코드를 열거하고, 이메일 보안 프로토콜을 감사하며, 서브도메인 탈취 취약점을 탐지합니다.
다른 이름 GuardBee/guardbee-mcp, @guardbee/mcp-dns-intelligence
- 스타
- 2
- Tools
- 6
- 다운로드, 30일
- 2,296
- 최신 버전
- 0.2.3
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- MIT
dns-intelligence MCP란?
dns-intelligence은(는) MCP server입니다. DNS 레코드를 열거하고, 이메일 보안 프로토콜을 감사하며, 서브도메인 탈취 취약점을 탐지합니다. 6개 도구를 제공합니다. 예: enumerate_dns, audit_domains, enumerate_subdomains.
프로젝트 README에서 생성된 요약
dns-intelligence MCP server 정보
보안 연구자와 개발자는 AI 클라이언트를 통해 직접 심층적인 DNS 감사 및 이메일 보안 평가를 수행할 수 있습니다. 이 서버는 A, MX, TXT를 포함한 다양한 DNS 레코드를 열거하는 도구를 제공하며, 도메인의 보안 상태에 따라 A–F 등급을 부여합니다. 특히 SPF, DMARC, DKIM 설정을 분석하여 과도한 룩업이나 정책 누락과 같은 설정 오류를 식별함으로써 이메일 인증을 집중적으로 점검합니다.
표준 레코드 조회 외에도, 이 서버는 Certificate Transparency 로그를 스캔하고 유실된 CNAME 레코드를 확인하여 잠재적인 서브도메인 탈취 취약점을 식별합니다. DKIM용 일반 셀렉터를 조사하고 DNSSEC 및 CAA 설정의 무결성을 평가할 수 있습니다. 사용자는 npx를 통해 로컬에서 이러한 검사를 실행하거나 제공된 MCP 도구를 사용하여 워크플로우에 통합할 수 있습니다. 이 시스템은 외부 종속성 없이 Node.js 내장 모듈을 사용하여 가볍게 설계되었으며, 텔레메트리는 기본적으로 비활성화 상태를 유지합니다.
활용 사례
- 1이메일 보안 프로토콜 감사도메인의 SPF, DMARC, DKIM 설정을 분석하여 구체적인 수정 권장 사항을 받습니다.
- 2서브도메인 탈취 위험 탐지유실된 CNAME 레코드를 확인하여 탈취에 취약한 서브도메인을 식별합니다.
- 3전체 DNS 열거 수행특정 도메인에 대한 모든 DNS 레코드의 종합 보고서와 보안 등급을 확인합니다.
- 4여러 도메인의 보안 등급 비교최대 20개의 서로 다른 도메인을 동시에 평가하여 보안 조사 결과를 비교합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
dns-intelligence MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 dns-intelligence MCP 설치
$ claude mcp add dns-intelligence -- npx -y @guardbee/mcp-dns-intelligenceCursor에 dns-intelligence MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"dns-intelligence": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}VS Code에 dns-intelligence MCP 설치
.vscode/mcp.json
{
"servers": {
"dns-intelligence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}VS Code CLI에 dns-intelligence MCP 설치
$ code --add-mcp '{"name":"dns-intelligence","type":"stdio","command":"npx","args":["-y","@guardbee/mcp-dns-intelligence"]}'Claude Desktop에 dns-intelligence MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"dns-intelligence": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}Codex에 dns-intelligence MCP 설치
$ codex mcp add dns-intelligence -- npx -y @guardbee/mcp-dns-intelligenceCodex config.toml에 dns-intelligence MCP 설치
~/.codex/config.toml
[mcp_servers.dns-intelligence] command = "npx" args = ["-y", "@guardbee/mcp-dns-intelligence"]
Gemini CLI에 dns-intelligence MCP 설치
$ gemini mcp add -s user dns-intelligence npx -- -y @guardbee/mcp-dns-intelligenceGemini settings.json에 dns-intelligence MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"dns-intelligence": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-dns-intelligence"
]
}
}
}dns-intelligence MCP 도구 6
README에서 감지됨enumerate_dnsaudit_domainsenumerate_subdomainscheck_takeovercheck_email_securitylookup_dns
| enumerate_dns | — | |
| audit_domains | — | |
| enumerate_subdomains | — | |
| check_takeover | — | |
| check_email_security | — | |
| lookup_dns | — |
자동 검사
2026년 11월 13일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨통과
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
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.
dns-intelligence MCP 질문
dns-intelligence MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add dns-intelligence -- npx -y @guardbee/mcp-dns-intelligence를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
dns-intelligence MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
dns-intelligence MCP는 어떤 도구를 제공하나요?
6개 도구를 제공합니다. 예: enumerate_dns, audit_domains, enumerate_subdomains, check_takeover, check_email_security.
어떤 DNS 레코드를 열거할 수 있나요?
이 서버는 A, AAAA, MX, NS, TXT, CNAME, SOA 레코드의 전체 열거를 지원합니다.
도구가 서브도메인 탈취를 어떻게 탐지하나요?
Certificate Transparency 로그와 워드리스트를 사용하여 일반적인 서브도메인을 조사한 다음, 점유 가능한 유실된 리소스가 있는지 CNAME 타겟을 확인합니다.
서버가 텔레메트리 데이터를 전송하나요?
텔레메트리는 기본적으로 비활성화되어 있습니다. GUARDBEE_TELEMETRY=1 환경 변수를 사용하여 활성화할 수 있습니다.
이메일 보안만 별도로 감사할 수 있나요?
네, 이 서버는 수정 권장 사항과 함께 SPF, DMARC, DKIM 통합 감사를 수행하는 도구를 제공합니다.