{"domain":"example.com","result":{"MX":[{"exchange":"","priority":0}]}}
curl --location --request GET 'https://zylalabs.com/api/13153/domain+name+records+lookup+api/26699/look+up+domain+records' --header 'Authorization: Bearer YOUR_API_KEY'
注册后,每个开发者都会被分配一个个人 API 访问密钥,这是一个唯一的字母和数字组合,用于访问我们的 API 端点。要使用 Domain Name Records Lookup API 进行身份验证,只需在 Authorization 标头中包含您的 bearer token。
| 标头 | 描述 |
|---|---|
授权
|
必需
应为 Bearer access_key. 订阅后,请查看上方的"您的 API 访问密钥"。
|
无长期承诺。随时升级、降级或取消。 免费试用包括最多 50 个请求。
(年度计费可节省 2 个月 🎉)
Live domain record lookups as structured data. Query nine record types of any domain or run a reverse lookup on a network address, and receive clean, machine-friendly answers.
Useful for domain onboarding and ownership checks, mail deliverability audits, monitoring name server changes, and enriching security logs.
The API returns structured data for nine record types: address (A and AAAA), mail exchange (MX), text (TXT), name server (NS), alias (CNAME), authority (SOA), certification authority (CAA), and service records (SRV). Users can query specific types or use the overview mode for common records.
The response includes the domain name and a result object keyed by record type. Each record type contains relevant fields, such as "exchange" and "priority" for MX records, or "address" for A records, providing essential details for each queried record.
响应数据以JSON格式组织,以域名作为主键,并包含按类型分类的记录数组的嵌套结果对象。每种记录类型的数据结构化以便于访问和解读
用户可以指定要查询的域名并选择记录类型(例如 A MX TXT)或者选择概览模式以在一次调用中检索多个常见记录类型 这种灵活性允许根据用户需求定制数据请求
Common use cases include domain onboarding, ownership verification, mail deliverability audits, monitoring name server changes, and enhancing security logs. The API provides essential insights for managing domain-related tasks effectively.
数据准确性通过来自权威DNS来源的定期更新得以维护 该API采用质量检查以确保返回的记录反映所查询域名的最新和可靠的信息
Users can leverage the structured response to integrate domain information into applications, perform audits, or monitor changes. For example, analyzing MX records can help assess mail server configurations, while A records can assist in verifying IP addresses.
If a queried record type has no data, the API returns a marker instead of failing the request. Users should check for these markers in the response to handle scenarios where certain records are unavailable, ensuring robust error handling in their applications.