Official vendor OpenAPI document · agent-readyData EnrichmentCompany DataapiKey168 EndpointsREST
For 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.
Use for: Check whether a domain is available to register, Look up the WHOIS record for a domain, Find all subdomains of a given domain, Detect the technology stack a website runs on
Not supported: Does not handle domain registration, DNS record editing, or SSL certificate issuance. Use for domain intelligence and OSINT lookups only.
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.
Install Jentic One Beta
Connect the DomScan to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DomScan, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdomscan.net%2Fdomscan" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdomscan.net%2Fdomscan" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with DomScan API.
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
Patterns agents use DomScan API for, with concrete tasks.
★ 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.
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.
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.
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.
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
168 endpoints — 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.
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
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
Jentic AI Readiness Score
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.
D
DomScan
- Foundational (C)54/100
47
Foundational Compliance64
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience58
Agent Usability50
Security81
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
47
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
87%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
7%
Example Density
How richly the API is illustrated with examples.
96%
Example Validity
Percentage of examples that conform to their schemas.
54%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
28%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
58
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: C+Signals: 1
58%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
81
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
81%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DomScan API through Jentic.
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.
GET STARTED