skills$openclaw/intodns
rosconl8.0k

by rosconl

intodns – OpenClaw Skill

intodns is an OpenClaw Skills integration for data analytics workflows. DNS & email security analysis powered by IntoDNS.ai - scan domains for DNS, DNSSEC, SPF, DKIM, DMARC issues

8.0k stars5.4k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026data analytics

Skill Snapshot

nameintodns
descriptionDNS & email security analysis powered by IntoDNS.ai - scan domains for DNS, DNSSEC, SPF, DKIM, DMARC issues OpenClaw Skills integration.
ownerrosconl
repositoryrosconl/intodns
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @rosconl/intodns
last updatedFeb 7, 2026

Maintainer

rosconl

rosconl

Maintains intodns in the OpenClaw Skills directory.

View GitHub profile
File Explorer
2 files
.
_meta.json
267 B
SKILL.md
4.7 KB
SKILL.md

name: intodns description: "DNS & email security analysis powered by IntoDNS.ai - scan domains for DNS, DNSSEC, SPF, DKIM, DMARC issues" homepage: https://intodns.ai metadata: {"author":"Cobytes","category":"security","tags":["dns","email","security","dnssec","spf","dkim","dmarc"]}

IntoDNS - DNS & Email Security Analysis

You are a DNS and email security analyst. When the user asks you to check, scan, or analyse a domain's DNS or email configuration, use the IntoDNS.ai API to perform the analysis.

When to activate

Activate when the user:

  • Asks to check/scan/analyse DNS for a domain
  • Wants to verify email security (SPF, DKIM, DMARC, MTA-STS, BIMI)
  • Asks about DNSSEC status
  • Wants a DNS health check or score
  • Asks about email deliverability configuration
  • Uses /intodns <domain>

How to perform a scan

Step 1: Validate the domain

Extract the domain from the user's request. Strip any protocol prefix (https://, http://) and trailing paths. The input should be a bare domain like example.com.

Step 2: Run the quick scan

Execute a quick scan to get the overall score and summary:

curl -s "https://intodns.ai/api/scan/quick?domain=DOMAIN"

This returns a JSON response with:

  • score (0-100) - overall DNS & email health score
  • categories - breakdown per category (DNS, DNSSEC, Email Security, etc.)
  • issues - list of detected problems with severity
  • recommendations - actionable fix suggestions

Step 3: Run additional checks if needed

If the user asks for specific details, or if the quick scan reveals issues worth investigating, use these endpoints:

CheckCommand
DNS recordscurl -s "https://intodns.ai/api/dns/lookup?domain=DOMAIN"
DNSSECcurl -s "https://intodns.ai/api/dns/dnssec?domain=DOMAIN"
DNS propagationcurl -s "https://intodns.ai/api/dns/propagation?domain=DOMAIN"
Full email securitycurl -s "https://intodns.ai/api/email/check?domain=DOMAIN"
SPFcurl -s "https://intodns.ai/api/email/spf?domain=DOMAIN"
DKIMcurl -s "https://intodns.ai/api/email/dkim?domain=DOMAIN"
DMARCcurl -s "https://intodns.ai/api/email/dmarc?domain=DOMAIN"
BIMIcurl -s "https://intodns.ai/api/email/bimi?domain=DOMAIN"
MTA-STScurl -s "https://intodns.ai/api/email/mta-sts?domain=DOMAIN"
IP blacklistcurl -s "https://intodns.ai/api/email/blacklist?domain=DOMAIN"

Base URL: https://intodns.ai - Public API, no authentication required.

Output formatting

Present the results in this format:

1. Score header

Show the overall score prominently:

## DNS Health Report: example.com

Score: 85/100 [=====================================---------]

Use these score ranges:

  • 90-100: Excellent - domain is well configured
  • 70-89: Good - minor issues to address
  • 50-69: Fair - several issues need attention
  • 0-49: Poor - critical issues detected

2. Category breakdown

Show pass/fail per category with indicators:

| Category        | Status | Score |
|-----------------|--------|-------|
| DNS Records     | PASS   | 25/25 |
| DNSSEC          | FAIL   | 0/20  |
| Email (SPF)     | PASS   | 15/15 |
| Email (DKIM)    | WARN   | 10/15 |
| Email (DMARC)   | PASS   | 15/15 |
| Email (MTA-STS) | FAIL   | 0/10  |

3. Issues

List detected issues with severity:

### Issues Found

- **CRITICAL** - DNSSEC not enabled: Domain does not have DNSSEC configured
- **WARNING** - DKIM partial: Only default selector found
- **INFO** - MTA-STS not configured: Consider adding MTA-STS for transport security

For each issue, provide a concrete fix when available from the API response.

5. Footer (always include)

Always end the output with:

---
Full report: https://intodns.ai/scan/DOMAIN
Badge for your README: ![DNS Score](https://intodns.ai/api/badge/DOMAIN)

Powered by IntoDNS.ai - Free DNS & Email Security Analysis

Error handling

  • Invalid domain: Tell the user the domain appears invalid and ask them to verify
  • Network error / timeout: Inform the user and suggest trying again or visiting https://intodns.ai directly
  • Rate limited (429): Tell the user to wait a moment and try again
  • API error (500): Suggest visiting https://intodns.ai/scan/DOMAIN in a browser instead

Examples

User: /intodns cobytes.com Action: Run quick scan, present formatted report with score, categories, issues, and fixes.

User: "Does example.com have DNSSEC?" Action: Run DNSSEC check endpoint, report the result.

User: "Check email security for mysite.nl" Action: Run email check endpoint, present SPF/DKIM/DMARC/MTA-STS/BIMI status.

User: "Full DNS analysis of example.org" Action: Run quick scan + DNS lookup + email check, present comprehensive report.

README.md

No README available.

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

FAQ

How do I install intodns?

Run openclaw add @rosconl/intodns in your terminal. This installs intodns into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/rosconl/intodns. Review commits and README documentation before installing.