# Reverse MX Examples

Worked Reverse MX examples: the domains that use a mail server, any mail server of its domain, with subdomains, paging and ordering.

Source: https://docs.deepinfo.com/reference/discovery/reverse-mx/examples/

Last updated: 2026-09-24

---
`GET https://api.deepinfo.com/v1/discovery/reverse-mx` · endpoint: [Reverse MX](/reference/discovery/reverse-mx/)

Worked examples for Reverse MX: the domains whose DNS MX record names a mail server. One example per parameter value (`apex`, `include_subdomains`), then paging and ordering. The mail servers are two public services: Google Workspace (`aspmx.l.google.com`) and Cloudflare Email Routing (`route1.mx.cloudflare.net`).

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.

## 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.extension.punycode` | The extension (TLD) |
| `dns_last_change_date` | The last change seen in the DNS records |
| `ssl_last_change_date` | The last change seen in the SSL certificate |
| `domain.whois_last_change_date` | The last change seen in the WHOIS record |
| `domain.whois.create_date` | The registration date |
| `domain.whois.expiry_date` | The expiry date |
| `domain.whois.update_date` | 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_format` | Used only with `export=true`: `json` (the default) or `csv`. |
| `export_scope` | Used only with `export=true`: `basic`, `default` or `extended` (how many fields each exported record carries). |

Each example links to its own page with the request and the response.

## Lookups

| Example | Param | Value |
|---|---|---|
| [Domains Using One Mail Server](/reference/discovery/reverse-mx/examples/mail-server/) | `mx` | `aspmx.l.google.com` |
| [Domains Using Cloudflare Email Routing](/reference/discovery/reverse-mx/examples/cloudflare-email-routing/) | `mx` | `route1.mx.cloudflare.net` |

## Options

| Example | Param | Value |
|---|---|---|
| [Any Mail Server Under the Same Domain](/reference/discovery/reverse-mx/examples/apex/) | `apex`<br>`mx` | `true`<br>`aspmx.l.google.com` |
| [Including Subdomains](/reference/discovery/reverse-mx/examples/include-subdomains/) | `include_subdomains`<br>`ordering`<br>`mx` | `true`<br>`punycode`<br>`route1.mx.cloudflare.net` |

## Paging

| Example | Param | Value |
|---|---|---|
| [Second Page of Results](/reference/discovery/reverse-mx/examples/second-page/) | `page`<br>`mx` | `2`<br>`aspmx.l.google.com` |
| [Larger Pages (100 Results)](/reference/discovery/reverse-mx/examples/page-size-100/) | `page_size`<br>`mx` | `100`<br>`aspmx.l.google.com` |

## Ordering

| Example | Param | Value |
|---|---|---|
| [Earliest Expiry First](/reference/discovery/reverse-mx/examples/ordering-expiry-date/) | `ordering`<br>`mx` | `domain.whois.expiry_date`<br>`route1.mx.cloudflare.net` |