Reverse NS Examples
Worked examples for Reverse NS: the domains whose DNS NS record names a name server. One example per parameter value (apex, include_subdomains), then paging and ordering. The name servers are Cloudflare’s may.ns.cloudflare.com (a shared name server of a large DNS provider) and Google’s ns1.google.com (used by Google’s own domains).
Every example is a real request with the response the API returned on September 24, 2026 (Deepinfo DEMO account); totals such as result_count change as the dataset is updated.
Responses are trimmed for display: results shows the first 3 records, long lists inside a record the first 10 items and very long texts the first 4,000 characters, while result_count stays the full total; each page says what was shortened. Personal data (WHOIS contact names, addresses, phone numbers and personal e-mail addresses) is redacted, and cookie values are masked (<value>).
Unless an example shows paging, it asks for page_size=25. page is 1 to 400 and page_size 25 to 100 (the API default is 100).
Each result is a full domain record, the same shape as a Domain Detail response: WHOIS, DNS, SSL certificate and web data.
After the examples: Ordering Values · Parameters Without an Example
- Endpoint
- Reverse NS
7 examples
No examples match these filters.
Lookups
| Example | Param | Value |
|---|---|---|
| Domains Using One Name Server | ns | may. |
| Domains on Google Name Servers | ns | ns1. |
Options
| Example | Param | Value |
|---|---|---|
| Any Name Server Under the Same Domain | apex ns | true may. |
| Including Subdomains | include_ ordering ns | true -punycode ns1. |
Paging
| Example | Param | Value |
|---|---|---|
| Second Page of Results | page ns | 2 may. |
| Larger Pages (100 Results) | page_ ns | 100 may. |
Ordering
| Example | Param | Value |
|---|---|---|
| Most Recent WHOIS Update First | ordering ns | -domain. ns1. |
Ordering Values
ordering sorts the results by one field, ascending; a leading - sorts descending (-domain.whois.create_date puts the newest registration first). Each value below was tried on the live API on September 24, 2026, on one of the Discovery endpoints, and sorted the results as described. Without ordering, the order is not fixed: the same request can return its records in a different order.
| Value | Sorts By |
|---|---|
punycode |
The domain name, in its ASCII (punycode) form |
domain. |
The extension (TLD) |
dns_ |
The last change seen in the DNS records |
ssl_ |
The last change seen in the SSL certificate |
domain. |
The last change seen in the WHOIS record |
domain. |
The registration date |
domain. |
The expiry date |
domain. |
The date the registry last updated the WHOIS record |
Parameters Without an Example
As of September 24, 2026, these parameters have no worked example.
| Parameter | Why |
|---|---|
export |
export=true returns the whole result set as a file download (JSON or CSV) instead of a page of results; these examples show paged JSON only. |
export_ |
Used only with export=true: json (the default) or csv. |
export_ |
Used only with export=true: basic, default or extended (how many fields each exported record carries). |