Skip to main content
POST
按 HTML 术语分类的域名
按 HTML 里出现的 search_terms 原始字符串匹配域名,而 post_dataforseo_domains_tech_domains_by_technology_live 匹配的是被识别出的技术。用于追踪代码片段、联盟标识或模板特征这类没有检测器命名的东西。返回 total_count、items_count、offset、offset_token 和 items,item 结构与技术搜索相同。单条实测 1.8 KB,用 limit 收口。响应包在 DataForSEO 的信封里:数据在 tasks[0].result,真正的成败在 tasks[0].status_code——请求被拒时 HTTP 仍然是 200,所以要看这个字段而不是传输层状态。

示例

第一次用? 把任意 MCP 客户端指向 https://mcp.aisa.one/mcp —— Claude Code、 Codex、Cursor、VS Code 都可以。鉴权走 OAuth:客户端打开浏览器,你点一次 Allow,不需要粘贴任何 key。各客户端的具体命令和每次调用的价格见 aisa.one/zh-cn/mcp。
在你的 agent 里把这个端点跑起来 →

授权

Authorization
string
header
必填

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

请求体

application/json
search_terms
string[]

target search terms
required field
specify target HTML elements, tags, attributes, their content or all of the above
if you specify more than one search term, you will receive only the domains containing all of the specified terms in the HTML code of their homepage
maximum number of search terms you can specify: 10
example:
["data-attrid"]

keywords
string[] | null

target keywords in the domain's title, description or meta keywords
optional field
UTF-8 encoding
maximum number of keywords you can specify: 10
example:
["seo","software"]

learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article

mode
string | null

search mode
optional field
possible search mode types:
strict_entry - search for results exactly matching the order, intervals and separators in the specified search terms
entry - search for results ignoring the order, intervals and separators in the specified search terms
default value: entry

filters
(object | null)[] | null

array of results filtering parameters
optional field
you can add several filters at once (8 filters maximum)
you should set a logical operator and, or between the conditions
the following operators are supported:
<, <=, >, >=, =, <>, in, not_in, like, not_like
you can use the % operator with like and not_like to match any string of zero or more characters
example:
["domain","like","%seo%"]

[["country_iso_code","=","US"],"and",["domain_rank",">",100]]

[["domain_rank",">",100],"and",[["country_iso_code","=","US"],"or",["country_iso_code","=","CA"]]]

for more information about filters, please refer to Domain Analytics Technologies API - Filters

order_by
string[] | null

results sorting rules
optional field
available fields:
domain_rank, domain, last_visited, country_iso_code, language_code, content_language_code
possible sorting types:
asc - results will be sorted in the ascending order
desc - results will be sorted in the descending order
you should use a comma to set up a sorting type
example:
["last_visited,desc"]
default rule:
["domain_rank,desc"]
note that you can set no more than three sorting rules in a single request
you should use a comma to separate several sorting rules
example:
["last_visited,desc","domain_rank,desc"]

limit
integer | null

the maximum number of returned domains
optional field
default value: 100
maximum value: 10000

offset
integer | null

offset in the results array of returned domains
optional field
default value: 0
if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive domains;
Note: the maximum value is 9999, the sum of limit and offset must not exceed 10000;
use the offset_token if you would like to offset more results

offset_token
string | null

token for subsequent requests
optional field
provided in the identical filed of the response to each request;
use this parameter to avoid timeouts while trying to obtain over 100,000 results in a single request;
by specifying the unique offset_token value from the response array, you will get the subsequent results of the initial task;
offset_token values are unique for each subsequent task
Note: if the offset_token is specified in the request, all other parameters should be identical to the previous request
learn more about this parameter on our Help Center

示例:

响应

object | null

Successful operation

version
string | null

API 的当前版本

status_code
integer | null

general status code you can find the full list of the response codes here

status_message
string | null

general informational message you can find the full list of general informational messages here

time
string | null

total execution time, seconds

cost
number<double> | null

任务总成本(美元)

tasks_count
integer<int64> | null

tasks 数组中的任务数量

tasks_error
integer<int64> | null

返回错误的 tasks 数组中的任务数量

tasks
(object | null)[] | null

array of tasks