Reference
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain |
string | yes | Domain or record name. Scheme, path and trailing dot are stripped. |
type |
string | no | ALL, A, AAAA, MX, TXT, NS, SOA, CNAME, CAA or SRV. Default: ALL. |
Example request
curl -s "https://api2.globus.studio/v2/dns?domain=globus.studio"
A DNS lookup decides whether a domain exists, where its mail goes and which certificate authority may issue for it. The endpoint returns every common record type in one JSON object, so a check does not need five terminal commands and a parser.
What the response contains
Records are grouped by type: A, AAAA, MX, TXT, NS, SOA, CNAME, SRV and CAA. TXT values are joined from chunks into whole strings, MX and SRV keep their priorities, and SOA keeps the serial and timers. CAA is reported with flags, tag and value.
curl -s "https://api2.globus.studio/v2/dns?domain=globus.studio"The services block answers two questions first: does www resolve, and can the domain receive mail. A null MX record, published as a single dot, sets mail to false because RFC 7505 means the domain refuses mail on purpose.
Type filter and limits
Add type=MX or type=TXT when only one record type matters, and the response contains one group. Underscore labels are accepted, so _sip._tcp.globus.studio works for SRV lookups.
Answers are cached for a minute and the whole lookup stops after three seconds. On a slow resolver the meta block sets partial to true and some groups come back empty. A public endpoint should return a partial answer faster than it should hold a connection, and this one does.
The response never promises a TTL per record: the resolver used here does not report it.
Related
The full parameter table, every error code and a live request are on the documentation page. It opens in the same language as this page and needs no account.
A longer walkthrough, with the checks that matter and the limits worth planning for: DNS records: one lookup instead of five.