@hasna/domains weekly downloads statistics

@hasna/domains

Domain portfolio, registrar, marketplace, and DNS management for AI agents. The package ships a CLI, MCP server, authenticated HTTP API, generated SDK, and library exports. Every client surface resolves its credential and authority through the one shared @hasna/contracts resolver (macOS Keychain, ~/.hasna/domains/config/credentials, or HASNA_DOMAINS_API_KEY, with the fleet gateway https://api.hasna.com/domains as the default authority), and data commands fail closed when no credential resolves: local SQLite path settings are rejected; domains-serve connects directly to cloud Postgres.

Features

• Domain portfolio management — track registrar, expiry, SSL, nameservers, pricing, lifecycle status, and notes • Registrar sync and purchase flows — direct Route 53 and Namecheap registration plus GoDaddy and Brandsight provider surfaces through a shared provider registry • Nameserver delegation — Route 53 and Namecheap adapters can update registrar nameservers when the provider API supports it • DNS provider management — create or reuse Cloudflare or Route 53 zones and manage DNS records through the DNS provider layer • DNS record CRUD — A, AAAA, CNAME, MX, TXT, NS, SRV records • DNS desired state — plan/diff/apply provider DNS records from JSON with explicit delete opt-in and post-apply verification • Sedo marketplace tools — optional search, portfolio/listing management, blacklist checks, and recorded Sedo purchases • AWS diagnostics — sync Route 53 registered domains and hosted zones without printing secret values • Credential diagnostics — redacted checks for Route 53, Cloudflare, Namecheap, GoDaddy, Brandsight, and Sedo • Expiry alerts — set alerts for domain expiry and SSL certificate expiry • WHOIS lookup — query and store registrar/expiry info from WHOIS • SSL certificate check — verify SSL issuer and expiry • DNS propagation check — query Google, Cloudflare, Quad9, OpenDNS • Zone file export/import — BIND-format zone files • Subdomain discovery — via crt.sh certificate transparency logs • DNS validation — detect CNAME conflicts, missing MX, and more • Portfolio export — CSV or JSON with all domain data • Brand monitoring — optional typosquat/threat detection via Brandsight API • MCP server — Model Context Protocol support for AI agents • MCP safe mode — expose read-only tools only with DOMAINS_MCP_SAFE_MODE=1 • HTTP API + SDK — authenticated /v1 API through domains-serve and a typed @hasna/domains/sdk client • Interactive TUI — optional portfolio browser in the terminal with domains interactive

Installation

All normal clients use the shared account API. Saved credentials live in the macOS Keychain or ~/.hasna/domains/config/credentials; HASNA_HOME and HASNA_CONFIG_HOME can select the credential root. Existing SQLite files are preserved for verified migration and are never opened by the CLI, MCP or SDK factory.

Optional Command Groups

The default CLI keeps core portfolio, registrar, DNS, provider, Route 53, doctor, MCP, and server commands loaded. Optional groups are enabled per invocation:

Available groups: brandsight, events, history, interactive, marketplace, outreach, owner, provision, research, wallet.

Quick Start

Provider Matrix

| Provider | Type | Availability | Buy/Register | Renew | Nameservers/DNS | Notes |

| route53 | registrar + DNS | yes | yes | no | nameservers + Route 53 hosted zones | Primary self-serve registration path. Use AWS_PROFILE or AWS keys. | | namecheap | registrar + DNS | yes | yes | yes | nameservers + Namecheap DNS records | Requires Namecheap API access and whitelisted client IP. | | godaddy | registrar + DNS | gated | no direct CLI purchase | gated | DNS records when API access qualifies | Availability remains threshold-gated; DNS/domain management is available for qualifying accounts. | | brandsight | registrar + DNS | yes | gated by contract | yes when contract allows | nameservers + DNS records | GoDaddy Corporate Domains / Brandsight v2 API; enterprise-contract-only. | | cloudflare | DNS + inventory | no | no | no | DNS zones and records | Preferred DNS provider; zone inventory syncs domains but does not prove registrar ownership. | | sedo | marketplace | marketplace search/status | recorded purchase only | no | no | Sedo is marketplace/listing/portfolio, not registrar DNS in this CLI. |

CLI Usage

dns add/update/remove changes the hosted portfolio. dns create instead contacts Cloudflare through its configured provider credential and creates exactly one previously absent DNS-only CNAME. Both the zone ID and zone name must match an active provider zone. Names and targets must be fully qualified; underscores in certificate-validation names are supported. An existing record of any type, including an identical CNAME, is refused without mutation.

The create command performs one POST and checks the returned record ID through both exact-ID and exact-name provider reads. It never updates, deletes, rolls back, or automatically retries a write. If a connection fails or readback does not match, inspect current provider state before deciding whether to try again. Provider CNAME collision handling protects competing address/CNAME creation; this operation is not a general compare-and-swap API for existing records.

dns set changes one existing live record in place by its record ID: it pins the zone, reads the record first for the exact pre-image, then issues one PATCH of only the fields given and verifies the readback. The record ID, type and name are preserved — nothing is deleted or recreated, and no retry is attempted. --expect-content refuses the change before any write unless the record still carries the reviewed content. It refuses without --yes, on any readback mismatch, when the record identity does not match, and on any id that is not an exact Cloudflare zone or record id.…

Description from the npm listing.