canonical: https://jentic.com/apis/domscan.net/domscan # DomScan The DomScan API analyzes a domain across availability, DNS, WHOIS, RDAP, certificates, and subdomains, then enriches it with technology-stack detection, IP geolocation, and reputation signals. It checks availability across 1,100+ TLDs singly or in bulk, detects typosquatting and lookalike domains for brand protection, and monitors a domain for expiration and availability changes. Most operations return structured JSON for a single domain or a batch, and credit-backed endpoints cover deeper OSINT such as certificate transparency search and exposed-software vulnerability scanning. ## For AI agents Check domain availability across 1,100+ TLDs, run DNS, WHOIS, and RDAP lookups, discover subdomains, detect a website's technology stack, and scan for typosquatting and lookalike domains. Supports single and bulk operations for domain intelligence and OSINT. ## Scope Does not handle domain registration, DNS record editing, or SSL certificate issuance. Use for domain intelligence and OSINT lookups only. ## Capabilities - Check domain availability across 1,100+ TLDs with RDAP, singly or in bulk - Run DNS record lookups, WHOIS, and RDAP queries, and compare answers across public recursive resolvers - Detect typosquatting and lookalike domains and generate a brand protection report - Discover subdomains and search certificate transparency logs for a domain - Detect a website's technology stack and scan exposed software for known vulnerabilities - Geolocate an IP address, trace a URL's redirect chain, and categorize a website - Monitor a brand for new lookalike domains with scheduled scans and alerts ## Use cases ### Agent-driven domain due diligence An AI agent connected through Jentic can vet a domain end to end: confirm whether it is registrable, pull its WHOIS and DNS records, discover live subdomains, and detect the technology stack behind it. DomScan returns structured JSON for each lookup so the agent can assemble a single report without scraping web pages, and bulk variants let it screen a list of domains in one pass. Example prompt: Check availability for a candidate domain, then pull its WHOIS record, DNS records, and live subdomains, and report the registrar, nameservers, and any discovered subdomains. ### Brand protection monitoring Security and brand teams use DomScan to find domains that impersonate their brand. The typosquatting endpoints generate permutations, run a live threat scan for registered lookalikes, and produce a protection report, while brand monitors run scheduled scans and raise alerts when a new lookalike appears. This supports takedown workflows and ongoing watchlists for a trademarked name. Example prompt: Run a live typosquatting threat scan for a brand domain, then create a brand monitor so new lookalike registrations trigger an alert. ### Attack-surface reconnaissance DomScan maps the external footprint of a domain for security assessments: subdomain discovery and certificate transparency search enumerate reachable hosts, technology detection fingerprints the stack each host runs, and the vulnerability scan flags exposed software with known issues. Combined with DNS security analysis, this gives an agent a prioritized view of a domain's attack surface from public sources only. Example prompt: Discover the subdomains of a target domain, detect the technology stack on each, and scan for exposed software with known vulnerabilities, then summarize the riskiest findings. ### Domain acquisition research For teams buying or shortlisting domains, DomScan estimates a domain's value, checks lifecycle and popularity, and scores candidate brand names, all returnable in bulk. An agent can rank a list of candidate names by availability and estimated value and flag which are already registered, turning a manual spreadsheet exercise into a single structured query. Example prompt: Score and value a shortlist of candidate domain names, check each for availability, and return a ranked list with estimated value and registration status. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/status` | Check single domain availability | | GET | `/v1/whois` | WHOIS lookup for a domain | | GET | `/v1/dns` | DNS record lookup | | GET | `/v1/subdomains` | Discover subdomains for a domain | | GET | `/v1/tech` | Detect a website's technology stack | | GET | `/v1/typos/threats` | Run a live typosquatting threat scan | | GET | `/v1/ip` | IP geolocation lookup | | POST | `/v1/brand-monitor` | Create a brand monitor | ## Key resources - **Availability & Lifecycle** — Check single or bulk domain availability across 1,100+ TLDs, plus lifecycle, popularity, and valuation data - **DNS, WHOIS & RDAP** — Resolve DNS records, run WHOIS and RDAP lookups, compare resolver answers, and query recorded WHOIS history - **Typosquatting & Brand Protection** — Generate typo permutations, run live threat scans, produce protection reports, and manage brand monitors - **Technology & Vulnerabilities** — Detect a website's technology stack, run bulk and asynchronous scans, and check exposed software for known vulnerabilities - **IP, Certificates & Subdomains** — Geolocate IP addresses, search certificate transparency logs, and discover subdomains for a domain ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 54 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 47 / 100 - Developer Experience & Jentic Compatibility: 64 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 58 / 100 - Security: 50 / 100 - AI Discoverability: 81 / 100 - **View full report:** https://jentic.com/apis/domscan.net/domscan/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring DomScan by hand means handling its API key auth, picking which of its many lookup operations you need, and coding retries for the 429 responses its rate limits return. Through Jentic you install once, import DomScan from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** DomScan carries the target domain in the query string rather than the URL path, so rules bound which operations your agent may call, not which domain it touches. You choose the operations it may call, so write operations such as creating or deleting a brand monitor are not included unless you add them. - **Credential handling:** Your DomScan API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'check if a domain is available' or 'look up a domain's WHOIS record', and Jentic returns the matching DomScan operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **DomainTools** — DomainTools offers domain profile, WHOIS, and DNS intelligence similar to DomScan's lookup surface - **IP2WHOIS** — IP2WHOIS is a focused WHOIS lookup service covering the same WHOIS data DomScan returns - **Threat Intelligence Platform** — Threat Intelligence Platform adds malware and infrastructure reputation data alongside DomScan's domain lookups - **IPGeolocation** — IPGeolocation provides detailed IP location and network data that complements DomScan's IP lookup ## FAQ ### What authentication does the DomScan API use? The DomScan API authenticates with an API key passed in the x-api-key header, per its OpenAPI spec. Most endpoints require the key, while selected reference and spec endpoints are public and need no credential. Through Jentic your key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context. ### Is there a DomScan MCP server? You don't need an MCP server to give your agent the DomScan API. Jentic connects it directly from the API Directory: import DomScan, store your key once, and your agent calls its operations. Because operations are discovered on demand, no extra server's tool definitions are loaded into the agent's context. ### Can I limit what my agent is allowed to do with the DomScan API? Yes. Write a rule that allows only the read lookups your agent needs, such as the availability, WHOIS, and DNS operations, so it can research domains but cannot create or delete a brand monitor, and every call it makes is logged. DomScan passes the target domain as a query parameter rather than in the URL path, so rules bound which operations run, not which domain they touch. ### Can I detect a website's technology stack with the DomScan API? Yes. The technology detection endpoint fingerprints the software a website runs, and bulk and asynchronous job variants let you scan many sites and retrieve results when they finish. A related endpoint scans the detected software for known vulnerabilities, so an agent can move from fingerprinting to risk assessment in the same workflow. ### What are the rate limits for the DomScan API? DomScan's spec documents a sustained limit of 120 requests per minute for free accounts and 600 requests per minute for paid accounts, with separate budgets for bulk endpoints; exceeding a limit returns HTTP 429 with a Retry-After header. Check the current figures at https://domscan.net/docs before relying on them in production. ### How do I run a domain intelligence lookup with the DomScan API through Jentic? Install Jentic One, import DomScan from the API Directory, and store your API key once. Your agent then searches by intent, for example 'check if a domain is available' or 'look up a domain's WHOIS record', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.