# DNS Lookup Free DNS lookup API. No auth, no API key. CORS enabled. ## Query (JSON) - use this one GET https://domainnamesystem.pages.dev/resolve?name=google.com GET https://domainnamesystem.pages.dev/resolve?name=google.com&type=A,AAAA,MX GET https://domainnamesystem.pages.dev/resolve?name=google.com&type=ALL Params: - name (required): domain name, e.g. google.com - type (optional): comma-separated record types. - omitted = default set: A, AAAA, CNAME, MX, TXT, NS - ALL = every supported type: A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, HTTPS, SRV, PTR - SRV and PTR only return data at special names (e.g. _sip._tcp.example.com, 10.2.0.192.in-addr.arpa), so they are usually empty for ordinary domains. Response: {"name":"google.com","status":"NOERROR","queried":["A","MX"],"answers":[{"name":"google.com","type":"A","ttl":300,"data":"142.250.x.x"}]} Fields: - status: DNS RCODE (NOERROR, NXDOMAIN, SERVFAIL, ...) - queried: the record types actually looked up - answers: records found (empty if none) - hint: present when the result needs interpreting (empty answers, errors, partial failure) - failed: present only on partial failure; types that returned SERVFAIL while others succeeded ## How to read the result - NXDOMAIN: the domain name does not exist. Definitive answer, not a lookup failure. - NOERROR with empty answers: the name exists but has no records of the queried types (normal for CNAME). - SERVFAIL: the upstream resolver could not get an answer (broken DNSSEC, dead name servers). Says nothing about whether the domain exists. Retry later. - Errors (HTTP 400) are JSON: {"error":"...","example":"..."}. ## MCP (Streamable HTTP, no auth) Endpoint: https://domainnamesystem.pages.dev/mcp Tool: dns_lookup {name, type?} ## A2A POST https://domainnamesystem.pages.dev/a2a (JSON-RPC message/send, protocol 0.3.0). Card: /.well-known/agent-card.json Send plain text ('google.com', 'MX gmail.com', 'what are the MX records of gmail.com') or a data part {"name":"gmail.com","type":"MX"}. The reply has a text part (JSON string) and a data part (parsed object). Streaming and tasks are not supported. ## Skill /.well-known/agent-skills/dns-lookup/SKILL.md (includes recipes: email setup, SPF/DMARC/DKIM, CAA, SRV, PTR) ## How it works Technical write-up (caching, ECS, CNAME flattening, HTTPS/ECH handling): https://domainnamesystem.pages.dev/how-it-works ## Raw DoH (RFC 8484) GET /?dns= or POST / with Content-Type: application/dns-message. ## Authenticity When enabled, JSON API responses carry RFC 9421 Signature, Signature-Input and Content-Digest headers. Public keys: /.well-known/http-message-signatures-directory ## Privacy Privacy policy: https://domainnamesystem.pages.dev/privacy-policy