What the API is for
Use DNSReach from monitoring systems, support tools, hosting panels or your own applications. Requests can return structured resolver, authoritative and geographic DNS evidence instead of HTML.
Typical jobs
Run a check, read its status, collect structured results and use the result in another system.
What it does not do
The API is not an open recursive DNS service and does not give unrestricted access to DNSReach infrastructure. Authentication, plan limits, rate limits and allowed operations still apply.
Separate service
Customer API traffic uses api.dnsreach.eu. Geographic nodes use a different controller address.
Authentication and limits
Paid API access uses account credentials or API tokens. Your account shows the limits that apply to your plan. Keys should never be placed in browser-side public code.
Plan access
Public evaluation information stays visible here. Exact keys, account limits and full endpoint documentation belong inside an eligible signed-in account.
Public documentation versus account documentation
Before buying, you should be able to understand what the API can do. We therefore publish the capability model and example flow publicly. Full endpoint reference, authentication examples and your enabled calls appear after sign-in when API access is active.
Example flow
POST /checks
GET /checks/{id}
GET /checks/{id}/resultsEndpoint names shown here describe the intended customer workflow. Your account documentation is the source for enabled production endpoints.