What Is My DNS Resolver
Creates a unique lookup name and reports the resolver that queries it, with browser and manual workflow support.
myresolver
v1
open
live-specialized-flow
Use This Skill
Endpoints
| Method | Path | Status | Modes |
|---|---|---|---|
| POST | /api/v1/myresolver/check |
live | json |
| GET | /api/v1/myresolver/result |
live | json |
Input Contract
Create a token with the check endpoint, query the returned hostname, then poll result with the token.
Output Contract
Returns pending/resolved status, resolver IP, provider identification where available, DNSSEC validation check, and timing metadata.
Errors
Token not found, token expired, or pending resolver result.
Auth and Limits
Anonymous for initial rollout.
Public low-volume use. Token TTL and polling limits apply.
Examples
Requests
POST /api/v1/myresolver/checkGET /api/v1/myresolver/result?token=...Responses
{"success":true,"status":"resolved","resolver_ip":"1.1.1.1"}FAQ
Why is this a multi-step skill?
Resolver detection requires a DNS query to a unique hostname, so the skill creates a correlation token first.