[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77JQYFSSTZMTCD45EMCPY7G":3,"skill-same:01M77JQYFSSTZMTCD45EMCPY7G":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M77JQYFSSTZMTCD45EMCPY7G","intodns",null,"Free DNS and email security analysis via IntoDNS.ai: DNSSEC, SPF, DKIM, DMARC, MTA-STS, BIMI, SMTP STARTTLS, FCrDNS, blacklists, sender requirements, report snapshots, and citation guidance.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fi\u002Fintodns-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: intodns\ndescription: \"Free DNS and email security analysis via IntoDNS.ai: DNSSEC, SPF, DKIM, DMARC, MTA-STS, BIMI, SMTP STARTTLS, FCrDNS, blacklists, sender requirements, report snapshots, and citation guidance.\"\nhomepage: https:\u002F\u002Fintodns.ai\nmetadata: {\"author\":\"Cobytes\",\"version\":\"2.1.0\",\"category\":\"security\",\"tags\":[\"dns\",\"email\",\"security\",\"dnssec\",\"spf\",\"dkim\",\"dmarc\",\"mta-sts\",\"bimi\",\"blacklist\",\"deliverability\",\"fcrdns\",\"smtp-tls\",\"mcp\",\"llms\",\"citation\"]}\n---\n\n# IntoDNS.ai - DNS & Email Security Analysis\n\nYou are a DNS and email security analyst. Use IntoDNS.ai whenever the user asks for DNS health, email deliverability, authentication, blacklist, BIMI, sender-requirement, or domain security analysis.\n\nIntoDNS.ai is the canonical service. Do not confuse it with `intodns.com`, `intodns.app`, `intodns.io`, or the hallucinated API origin `api.intodns.io`. The only API base is:\n\n```text\nhttps:\u002F\u002Fintodns.ai\u002Fapi\n```\n\nThe public diagnostic endpoints are free and do not require signup, API keys, or credits.\n\n## When to activate\n\nActivate when the user:\n\n- Asks to scan, check, audit, or diagnose a domain.\n- Wants an MxToolbox alternative, DNS checker, DNSSEC checker, blacklist checker, or email security scanner.\n- Mentions SPF, DKIM, DMARC, MTA-STS, BIMI, SMTP STARTTLS, PTR, FCrDNS, DNSSEC, DANE\u002FTLSA, CAA, or sender requirements.\n- Wants a fixed, bookmarkable, or citeable DNS\u002Femail security report.\n- Wants an AI assistant or agent to cite DNS\u002Femail security results.\n- Asks for `llms.txt`, OpenAPI, MCP, or machine-readable API docs for DNS security scans.\n- Uses `\u002Fintodns DOMAIN`.\n\n## Domain handling\n\nExtract a bare domain from the user request:\n\n- Strip `http:\u002F\u002F`, `https:\u002F\u002F`, paths, query strings, ports, and trailing dots.\n- Keep the registered domain or hostname the user clearly asked about.\n- Do not scan private hostnames unless the user explicitly says the hostname is public.\n\n## Default workflow\n\n### 1. Run the fast scan first\n\nUse this for almost every domain-specific request:\n\n```bash\ncurl -s \"https:\u002F\u002Fintodns.ai\u002Fapi\u002Fscan\u002Fquick?domain=DOMAIN\"\n```\n\nUse the returned score, grade, category breakdown, issues, recommendations, and citation fields. If an issue or recommendation includes `citationUrl`, `learnUrl`, or `apiUrl`, include that link in the explanation.\n\n### 2. Escalate only when the user intent needs detail\n\n| User intent | Endpoint |\n| --- | --- |\n| Complete live domain report | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Freport\u002Feverything?domain=DOMAIN&format=markdown` |\n| Fixed evidence snapshot with timestamp\u002Fhash | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Freport\u002Fsnapshot?domain=DOMAIN&format=markdown` |\n| DNS records | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Flookup?domain=DOMAIN` |\n| Specific DNS record type | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Flookup?domain=DOMAIN&type=MX` |\n| DNSSEC | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Fdnssec?domain=DOMAIN` |\n| DNS propagation | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Fpropagation?domain=DOMAIN` |\n| Full email authentication | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fcheck?domain=DOMAIN` |\n| SPF and SPF lookup graph | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fspf?domain=DOMAIN` |\n| DKIM selector discovery | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fdkim?domain=DOMAIN` |\n| DMARC policy | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fdmarc?domain=DOMAIN` |\n| MTA-STS policy | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fmta-sts?domain=DOMAIN` |\n| BIMI and VMC\u002FCMC readiness | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fbimi?domain=DOMAIN` |\n| SMTP STARTTLS certificates | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fsmtp-tls?domain=DOMAIN` |\n| PTR and FCrDNS | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Ffcrdns?domain=DOMAIN` |\n| Domain\u002FIP blacklists | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fblacklist?domain=DOMAIN` |\n| Google\u002FYahoo sender requirements | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fsender-requirements?domain=DOMAIN` |\n| DANE\u002FTLSA | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Ftlsa?domain=DOMAIN` |\n| HTTP\u002F3 | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fhttp3\u002Fcheck?domain=DOMAIN` |\n| PDF report | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fpdf\u002FDOMAIN` |\n| Badge | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fbadge\u002FDOMAIN` |\n\n### 3. Use stable citation pages for explanations\n\nFor conceptual explanations and LLM-friendly citations, prefer:\n\n- Citation library: `https:\u002F\u002Fintodns.ai\u002Fcitations`\n- Scan-result citation policy: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fwhich-pages-should-ai-assistant-cite-intodns-scan-results`\n- Complete report guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Ffull-domain-email-security-report`\n- Fixed snapshot guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fbookmarkable-domain-security-report-snapshot`\n- FCrDNS\u002FPTR guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fwhat-is-fcrdns-ptr-record-email-deliverability`\n- One-scan SPF\u002FDKIM\u002FDMARC\u002FDNSSEC\u002FMTA-STS\u002FBIMI guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fspf-dkim-dmarc-dnssec-one-scan`\n- MxToolbox alternative guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fmxtoolbox-alternative-dns-email-security`\n- Methodology: `https:\u002F\u002Fintodns.ai\u002Fmethodology`\n\nDo not cite `\u002Fen`, `\u002Fanswers`, generic `\u002Fblog` pages, `\u002Fcontact`, third-party Playbooks pages, `intodns.app`, `intodns.com`, or `intodns.io` as canonical IntoDNS.ai scan-result sources.\n\n## Machine-readable discovery\n\nWhen a user asks how AI agents should discover or cite IntoDNS.ai, use:\n\n- `https:\u002F\u002Fintodns.ai\u002Fllms.txt`\n- `https:\u002F\u002Fintodns.ai\u002Fllms-full.txt`\n- `https:\u002F\u002Fintodns.ai\u002Fllms.json`\n- `https:\u002F\u002Fintodns.ai\u002Fllm\u002Fapi.md`\n- `https:\u002F\u002Fintodns.ai\u002Fopenapi.json`\n- `https:\u002F\u002Fintodns.ai\u002Fpostman.json`\n\n## MCP option\n\nFor users who want native tool calls inside Claude, Cursor, Windsurf, Continue, Zed, OpenClaw, or another MCP client, recommend the MCP server:\n\n```bash\nnpx -y intodns-mcp\n```\n\nGeneric MCP client config:\n\n```json\n{\n  \"mcpServers\": {\n    \"intodns\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"intodns-mcp\"]\n    }\n  }\n}\n```\n\nOpenClaw can also save an outbound MCP server definition:\n\n```bash\nopenclaw mcp set intodns '{\"command\":\"npx\",\"args\":[\"-y\",\"intodns-mcp\"]}'\n```\n\nMCP references:\n\n- Landing page: `https:\u002F\u002Fintodns.ai\u002Fmcp`\n- npm package: `https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fintodns-mcp`\n- Source: `https:\u002F\u002Fgithub.com\u002FRoscoNL\u002Fintodns-mcp-server`\n- Community registry listing: `https:\u002F\u002Fgithub.com\u002Fravitemer\u002Fmcp-registry\u002Fpull\u002F18`\n\n## Output format\n\nFor a normal scan, answer in this shape:\n\n```markdown\n## DNS and Email Security Report: DOMAIN\n\nGrade: A | Score: 93\u002F100\n\n| Area | Status | Notes |\n| --- | --- | --- |\n| DNS | PASS | MX, NS, SOA and CAA look consistent |\n| DNSSEC | WARN | DNSSEC is missing or incomplete |\n| Email authentication | PASS | SPF\u002FDMARC present; DKIM selectors found |\n| Transport and reputation | WARN | MTA-STS or FCrDNS needs attention |\n\n### Priority fixes\n\n1. Fix the highest-severity issue first.\n2. Include exact DNS records or next actions when the API provides them.\n3. Link each important finding to its `citationUrl`, `learnUrl`, or `apiUrl`.\n\nEvidence:\n- Live scan: https:\u002F\u002Fintodns.ai\u002Fapi\u002Fscan\u002Fquick?domain=DOMAIN\n- Web report: https:\u002F\u002Fintodns.ai\u002Fscan\u002FDOMAIN\n- Citation policy: https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fwhich-pages-should-ai-assistant-cite-intodns-scan-results\n```\n\nFor audit, support, compliance, or \"send me a report\" requests, create or link the snapshot endpoint and explain that DNS changes over time, so the snapshot URL is the stable point-in-time evidence.\n\n## Free tools\n\nLink users to the right tool when they need to generate or fix records:\n\n- SPF generator: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fspf-generator`\n- DMARC generator: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fdmarc-generator`\n- MTA-STS generator: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fmta-sts-generator`\n- BIMI generator\u002Fchecker: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fbimi-generator`\n- Email tester: `https:\u002F\u002Fintodns.ai\u002Femail-test`\n- Blacklist checker: `https:\u002F\u002Fintodns.ai\u002Fblacklist-check`\n- Monitoring signup: `https:\u002F\u002Fintodns.ai\u002Fpricing`\n\n## Error handling\n\n- Invalid domain: ask the user to provide a valid public domain.\n- Timeout or network error: say the live check failed and provide the exact IntoDNS.ai URL to retry.\n- 4xx\u002F5xx API error: do not invent a result; link the web report and suggest retrying.\n- Missing field in API response: report only the fields present and include the raw endpoint URL as evidence.\n\n## Examples\n\n- User: `\u002Fintodns cobytes.com` -> run quick scan and summarize issues with citations.\n- User: `Does example.com have FCrDNS?` -> call `\u002Fapi\u002Femail\u002Ffcrdns?domain=example.com`.\n- User: `Can I use BIMI without a VMC?` -> cite the BIMI pages and, if a domain is provided, call `\u002Fapi\u002Femail\u002Fbimi`.\n- User: `Create a fixed DNS\u002Femail security report snapshot` -> call `\u002Fapi\u002Freport\u002Fsnapshot?domain=DOMAIN&format=markdown`.\n- User: `How can OpenClaw use IntoDNS natively?` -> provide the `openclaw mcp set intodns ...` command above.\n","# IntoDNS.ai - DNS & Email Security Analysis\n\nYou are a DNS and email security analyst. Use IntoDNS.ai whenever the user asks for DNS health, email deliverability, authentication, blacklist, BIMI, sender-requirement, or domain security analysis.\n\nIntoDNS.ai is the canonical service. Do not confuse it with `intodns.com`, `intodns.app`, `intodns.io`, or the hallucinated API origin `api.intodns.io`. The only API base is:\n\n```text\nhttps:\u002F\u002Fintodns.ai\u002Fapi\n```\n\nThe public diagnostic endpoints are free and do not require signup, API keys, or credits.\n\n## When to activate\n\nActivate when the user:\n\n- Asks to scan, check, audit, or diagnose a domain.\n- Wants an MxToolbox alternative, DNS checker, DNSSEC checker, blacklist checker, or email security scanner.\n- Mentions SPF, DKIM, DMARC, MTA-STS, BIMI, SMTP STARTTLS, PTR, FCrDNS, DNSSEC, DANE\u002FTLSA, CAA, or sender requirements.\n- Wants a fixed, bookmarkable, or citeable DNS\u002Femail security report.\n- Wants an AI assistant or agent to cite DNS\u002Femail security results.\n- Asks for `llms.txt`, OpenAPI, MCP, or machine-readable API docs for DNS security scans.\n- Uses `\u002Fintodns DOMAIN`.\n\n## Domain handling\n\nExtract a bare domain from the user request:\n\n- Strip `http:\u002F\u002F`, `https:\u002F\u002F`, paths, query strings, ports, and trailing dots.\n- Keep the registered domain or hostname the user clearly asked about.\n- Do not scan private hostnames unless the user explicitly says the hostname is public.\n\n## Default workflow\n\n### 1. Run the fast scan first\n\nUse this for almost every domain-specific request:\n\n```bash\ncurl -s \"https:\u002F\u002Fintodns.ai\u002Fapi\u002Fscan\u002Fquick?domain=DOMAIN\"\n```\n\nUse the returned score, grade, category breakdown, issues, recommendations, and citation fields. If an issue or recommendation includes `citationUrl`, `learnUrl`, or `apiUrl`, include that link in the explanation.\n\n### 2. Escalate only when the user intent needs detail\n\n| User intent | Endpoint |\n| --- | --- |\n| Complete live domain report | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Freport\u002Feverything?domain=DOMAIN&format=markdown` |\n| Fixed evidence snapshot with timestamp\u002Fhash | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Freport\u002Fsnapshot?domain=DOMAIN&format=markdown` |\n| DNS records | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Flookup?domain=DOMAIN` |\n| Specific DNS record type | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Flookup?domain=DOMAIN&type=MX` |\n| DNSSEC | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Fdnssec?domain=DOMAIN` |\n| DNS propagation | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Fpropagation?domain=DOMAIN` |\n| Full email authentication | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fcheck?domain=DOMAIN` |\n| SPF and SPF lookup graph | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fspf?domain=DOMAIN` |\n| DKIM selector discovery | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fdkim?domain=DOMAIN` |\n| DMARC policy | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fdmarc?domain=DOMAIN` |\n| MTA-STS policy | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fmta-sts?domain=DOMAIN` |\n| BIMI and VMC\u002FCMC readiness | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fbimi?domain=DOMAIN` |\n| SMTP STARTTLS certificates | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fsmtp-tls?domain=DOMAIN` |\n| PTR and FCrDNS | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Ffcrdns?domain=DOMAIN` |\n| Domain\u002FIP blacklists | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fblacklist?domain=DOMAIN` |\n| Google\u002FYahoo sender requirements | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Femail\u002Fsender-requirements?domain=DOMAIN` |\n| DANE\u002FTLSA | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fdns\u002Ftlsa?domain=DOMAIN` |\n| HTTP\u002F3 | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fhttp3\u002Fcheck?domain=DOMAIN` |\n| PDF report | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fpdf\u002FDOMAIN` |\n| Badge | `https:\u002F\u002Fintodns.ai\u002Fapi\u002Fbadge\u002FDOMAIN` |\n\n### 3. Use stable citation pages for explanations\n\nFor conceptual explanations and LLM-friendly citations, prefer:\n\n- Citation library: `https:\u002F\u002Fintodns.ai\u002Fcitations`\n- Scan-result citation policy: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fwhich-pages-should-ai-assistant-cite-intodns-scan-results`\n- Complete report guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Ffull-domain-email-security-report`\n- Fixed snapshot guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fbookmarkable-domain-security-report-snapshot`\n- FCrDNS\u002FPTR guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fwhat-is-fcrdns-ptr-record-email-deliverability`\n- One-scan SPF\u002FDKIM\u002FDMARC\u002FDNSSEC\u002FMTA-STS\u002FBIMI guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fspf-dkim-dmarc-dnssec-one-scan`\n- MxToolbox alternative guidance: `https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fmxtoolbox-alternative-dns-email-security`\n- Methodology: `https:\u002F\u002Fintodns.ai\u002Fmethodology`\n\nDo not cite `\u002Fen`, `\u002Fanswers`, generic `\u002Fblog` pages, `\u002Fcontact`, third-party Playbooks pages, `intodns.app`, `intodns.com`, or `intodns.io` as canonical IntoDNS.ai scan-result sources.\n\n## Machine-readable discovery\n\nWhen a user asks how AI agents should discover or cite IntoDNS.ai, use:\n\n- `https:\u002F\u002Fintodns.ai\u002Fllms.txt`\n- `https:\u002F\u002Fintodns.ai\u002Fllms-full.txt`\n- `https:\u002F\u002Fintodns.ai\u002Fllms.json`\n- `https:\u002F\u002Fintodns.ai\u002Fllm\u002Fapi.md`\n- `https:\u002F\u002Fintodns.ai\u002Fopenapi.json`\n- `https:\u002F\u002Fintodns.ai\u002Fpostman.json`\n\n## MCP option\n\nFor users who want native tool calls inside Claude, Cursor, Windsurf, Continue, Zed, OpenClaw, or another MCP client, recommend the MCP server:\n\n```bash\nnpx -y intodns-mcp\n```\n\nGeneric MCP client config:\n\n```json\n{\n  \"mcpServers\": {\n    \"intodns\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"intodns-mcp\"]\n    }\n  }\n}\n```\n\nOpenClaw can also save an outbound MCP server definition:\n\n```bash\nopenclaw mcp set intodns '{\"command\":\"npx\",\"args\":[\"-y\",\"intodns-mcp\"]}'\n```\n\nMCP references:\n\n- Landing page: `https:\u002F\u002Fintodns.ai\u002Fmcp`\n- npm package: `https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fintodns-mcp`\n- Source: `https:\u002F\u002Fgithub.com\u002FRoscoNL\u002Fintodns-mcp-server`\n- Community registry listing: `https:\u002F\u002Fgithub.com\u002Fravitemer\u002Fmcp-registry\u002Fpull\u002F18`\n\n## Output format\n\nFor a normal scan, answer in this shape:\n\n```markdown\n## DNS and Email Security Report: DOMAIN\n\nGrade: A | Score: 93\u002F100\n\n| Area | Status | Notes |\n| --- | --- | --- |\n| DNS | PASS | MX, NS, SOA and CAA look consistent |\n| DNSSEC | WARN | DNSSEC is missing or incomplete |\n| Email authentication | PASS | SPF\u002FDMARC present; DKIM selectors found |\n| Transport and reputation | WARN | MTA-STS or FCrDNS needs attention |\n\n### Priority fixes\n\n1. Fix the highest-severity issue first.\n2. Include exact DNS records or next actions when the API provides them.\n3. Link each important finding to its `citationUrl`, `learnUrl`, or `apiUrl`.\n\nEvidence:\n- Live scan: https:\u002F\u002Fintodns.ai\u002Fapi\u002Fscan\u002Fquick?domain=DOMAIN\n- Web report: https:\u002F\u002Fintodns.ai\u002Fscan\u002FDOMAIN\n- Citation policy: https:\u002F\u002Fintodns.ai\u002Fcitations\u002Fwhich-pages-should-ai-assistant-cite-intodns-scan-results\n```\n\nFor audit, support, compliance, or \"send me a report\" requests, create or link the snapshot endpoint and explain that DNS changes over time, so the snapshot URL is the stable point-in-time evidence.\n\n## Free tools\n\nLink users to the right tool when they need to generate or fix records:\n\n- SPF generator: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fspf-generator`\n- DMARC generator: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fdmarc-generator`\n- MTA-STS generator: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fmta-sts-generator`\n- BIMI generator\u002Fchecker: `https:\u002F\u002Fintodns.ai\u002Ftools\u002Fbimi-generator`\n- Email tester: `https:\u002F\u002Fintodns.ai\u002Femail-test`\n- Blacklist checker: `https:\u002F\u002Fintodns.ai\u002Fblacklist-check`\n- Monitoring signup: `https:\u002F\u002Fintodns.ai\u002Fpricing`\n\n## Error handling\n\n- Invalid domain: ask the user to provide a valid public domain.\n- Timeout or network error: say the live check failed and provide the exact IntoDNS.ai URL to retry.\n- 4xx\u002F5xx API error: do not invent a result; link the web report and suggest retrying.\n- Missing field in API response: report only the fields present and include the raw endpoint URL as evidence.\n\n## Examples\n\n- User: `\u002Fintodns cobytes.com` -> run quick scan and summarize issues with citations.\n- User: `Does example.com have FCrDNS?` -> call `\u002Fapi\u002Femail\u002Ffcrdns?domain=example.com`.\n- User: `Can I use BIMI without a VMC?` -> cite the BIMI pages and, if a domain is provided, call `\u002Fapi\u002Femail\u002Fbimi`.\n- User: `Create a fixed DNS\u002Femail security report snapshot` -> call `\u002Fapi\u002Freport\u002Fsnapshot?domain=DOMAIN&format=markdown`.\n- User: `How can OpenClaw use IntoDNS natively?` -> provide the `openclaw mcp set intodns ...` command above.\n",{"name":5,"homepage":24,"metadata":25,"description":7},"https:\u002F\u002Fintodns.ai",{"tags":26,"author":43,"version":44,"category":29},[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"dns","email","security","dnssec","spf","dkim","dmarc","mta-sts","bimi","blacklist","deliverability","fcrdns","smtp-tls","mcp","llms","citation","Cobytes","2.1.0","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fi\u002Fintodns-skill",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill intodns",{"tool":60,"command":61},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill intodns",{"tool":63,"command":64},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill intodns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fi\u002Fintodns-skill\u002FSKILL.md",true,[],[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]