360 Secure SkillHub
360 安全技能中心

Domainion Ops

核心功能涵盖域名注册、可用性查询、续费、转移，DNS全类型记录（A、MX等）管理、域名服务器切换、重定向设置、解析生效验证等。默认使用name.com，用户可指定GoDaddy或Namecheap，操作前需配置对应服务商凭据。典型场景包括新域名注册、调整网站解析、切换域名服务商、验证解析是否生效等，通过触发关键词（如“注册域名”“添加DNS记录”）启动操作，操作含防护机制避免误操作，执行后反馈结果。

iahmadzain
iahmadzain
热度 85.07
最近更新 2026-05-17 13:10:50
分类：自动化依赖：第三方 API / 代码执行应用场景：API 集成 / 自动化脚本 / 工作流 / DevOps

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add domainion-ops
Metadata
name
domainion-ops
description
Domain and DNS operations across name.com (default), GoDaddy, and Namecheap. Use for registering domains, flipping nameservers, managing DNS records (A, AAAA, CNAME, MX, TXT, NS, SRV), setting up redirects, checking domain availability, renewals, transfers, and verifying DNS propagation. Default provider is name.com unless the user selects GoDaddy or Namecheap. Triggers on: "register domain", "add DNS record", "change nameservers", "check domain availability", "transfer domain", "renew domain", "set up redirect", "DNS propagation check", "update MX record", "point domain to".

Domainion Ops

Multi-provider domain and DNS management. Default provider: name.com.

Provider Selection

Provider When to use Reference
name.com (default) Unless user specifies otherwise references/name-com.md
GoDaddy User says "GoDaddy" or has GoDaddy account references/godaddy.md
Namecheap User says "Namecheap" or has Namecheap account references/namecheap.md

Read only the relevant provider reference. Do not load all three.

Credentials Setup

Before any operation, verify credentials exist. Store in env or ~/.domainion:

# name.com (default)
NAMECOM_USERNAME=your_username
NAMECOM_TOKEN=your_api_token      # name.com > Account > API Settings

# GoDaddy
GODADDY_API_KEY=your_key
GODADDY_API_SECRET=your_secret   # developer.godaddy.com > API Keys

# Namecheap
NAMECHEAP_USERNAME=your_username
NAMECHEAP_API_KEY=your_api_key   # namecheap.com > Profile > Tools > API Access
NAMECHEAP_CLIENT_IP=your_ip      # Your whitelisted IP

If credentials are missing, prompt the user for the relevant provider's creds before proceeding.

Common Workflows

1. Check domain availability

# name.com (default)
curl -u "$NAMECOM_USERNAME:$NAMECOM_TOKEN" \
  "https://api.name.com/v4/domains:checkAvailability" \
  -d '{"domainNames":["example.com"]}'

→ See provider reference for GoDaddy / Namecheap equivalents.

2. DNS record management (add/update/delete)

Load provider reference for exact API calls. General pattern:

  • List records first to confirm state
  • Add or Update with idempotency check (avoid duplicates)
  • Verify with dig after change

3. Nameserver change

Always confirm registrar before changing NS. Wrong registrar = silent failure. Load provider reference for exact API call.

4. Verify DNS propagation

# Primary check (Cloudflare resolver — fast TTL)
dig +short example.com @1.1.1.1

# Authoritative check
dig +short example.com @8.8.8.8

# Full record check
dig example.com ANY +noall +answer

# HTTP redirect verify
curl -sI https://example.com | grep -i location

5. TTL Strategy

  • Lowering TTL before a change: set to 300 (5 min) at least 1 TTL cycle before
  • After change confirmed: restore to 3600 or higher
  • Never lower TTL after making the change — too late

Guardrails

  • Confirm domain + provider before any destructive action (NS change, record delete)
  • List existing records before adding to avoid duplicates
  • Prefer reversible steps; verify after each change
  • Never expose API tokens/secrets in output
  • For MX changes: always keep at least one valid MX record live during migration