Reverse MX Examples

GEThttps://api.deepinfo.com/v1/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.

After the examples: Ordering Values · Parameters Without an Example

Endpoint: Reverse MX

Lookups

Example	Param	Value
Domains Using One Mail Server	mx	aspmx.l.google.com
Domains Using Cloudflare Email Routing	mx	route1.mx.cloudflare.net

Options

Example	Param	Value
Any Mail Server Under the Same Domain	apex mx	true aspmx.l.google.com
Including Subdomains	include_subdomains ordering mx	true punycode route1.mx.cloudflare.net

Paging

Example	Param	Value
Second Page of Results	page mx	2 aspmx.l.google.com
Larger Pages (100 Results)	page_size mx	100 aspmx.l.google.com

Ordering

Example	Param	Value
Earliest Expiry First	ordering mx	domain.whois.expiry_date route1.mx.cloudflare.net

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).

Reference updated September 24, 2026