Find every domain on an MX record.
Pass an MX record value. Get back every domain that routes mail through it. Useful for spam-infrastructure clustering and email-vendor mapping.
One pivot from MX to its full footprint.
The Reverse MX API queries the indexed corpus for every domain whose MX records point at a given target. Match is on current or historical MX state; the response metadata distinguishes.
Pass the MX hostname (without priority prefix). Use apex and include_subdomains to scope.
This API is the right pivot for spam-infrastructure attribution and for mapping email-routing patterns across vendor portfolios. Legitimate clusters anchor on Google Workspace, Microsoft 365, and a handful of major hosts; outliers are usually interesting.
One endpoint, one required parameter.
Endpoint:
GET https://api.deepinfo.com/v1/discovery/reverse-mx?mx={mx}
Parameters:
Authentication is by API token in the request header. See docs.deepinfo.com for the full request reference.
See what the API returns.
Real response structure for the Find every domain on an MX record endpoint. Field coverage may vary based on query parameters and data availability.
{
"_request": {"mx": "mail.example-host.com"},
"results": [
{"fqdn": "small-business-1.com", "mx_first_seen": "2024-02-08"},
{"fqdn": "small-business-2.io", "mx_first_seen": "2024-04-15"},
{"fqdn": "spam-relay-front.net", "mx_first_seen": "2025-11-22"}
],
"pagination": {"page": 1, "page_size": 50, "total": 84}
}
Sample response shown. Real responses depend on query parameters, data availability, and API version. Talk to us for full schema documentation.
Workflows this API plugs into directly.
Threat Hunting
Cluster spam and phishing-infrastructure by shared MX targets.
Read the use caseIncident Investigation and Response
Pivot from an MX record surfaced in email telemetry to the full domain footprint.
Read the use casePhishing Detection and Prevention
Map the email-routing infrastructure behind a confirmed phishing campaign.
Read the use case“MX-clustering catches spam infrastructure that no other pivot reveals. Routing this through one API instead of running our own passive-DNS scrape pipeline freed engineering cycles for actual detection work.”
Other lookup APIs.
Current Whois state for any domain, in one call.
The Whois Lookup API returns the registration record for a domain right now: registrar, dates, registrant, name servers, and status codes.
See API APICurrent IP allocation state, in one call.
Pass an IP address.
See API APICurrent DNS state for an FQDN, in one call.
Pass an FQDN and one or more record types.
See API APICurrent TLS state for a host, in one call.
Pass a domain or IP.
See API APIFind every domain on a name server.
Pass a name server hostname.
See API APIFind every domain on an IP.
Pass an IP address or CIDR.
See API APICapture a target page as the user sees it.
Pass a URL.
See API APIDetect the technology stack of a target, in one call.
Pass a URL.
See API APILive web-page data for a target, in one call.
Pass a URL.
See API APIScan a target's open ports, in one call.
Pass a target.
See APIRun a reverse-MX pivot, from any hostname.
We'll set up token access and walk through how teams plug this into anti-phishing workflows.