OSINT 1 Endpoints 8 Key Features

Reverse MX Lookup (Deprecated) API

Deprecated: this endpoint performs exact-hostname searches only against a best-effort seven-day index populated by prior /v1/dns/all lookups. Each MX host keeps at most 10,000 recent entries. The API evaluates limit entries before returning one row per apex by default, and it is not an internet-wide dataset.

Category OSINT
Endpoints 1
Key Features 8
Frequently Asked Questions 4

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

1
Authenticate once

Send your API key with the documented header and keep requests consistent across services.

2
Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

3
Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

mx
Response fields

Example Response

queryquery.mxquery.matchquery.include_apex_onlydeprecateddeprecation_noticeresultssummarysummary.total_foundsummary.returnedfreshness_summaryfreshness_summary.source
Status coverage

HTTP Status Codes

200400401402429500502503504

Endpoints

GET /v1/reverse/mx
Credits: 2Authentication: Authentication required
mx

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign Up for Free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example Request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Deprecated cache lookup

Returns only the most recent limit entries from the per-host best-effort index populated by /v1/dns/all lookups, with apex deduplication enabled by default.

Not internet-wide

This endpoint does not crawl DNS, zone files, or a complete passive DNS corpus.

Legacy signal

Use results as optional context, not as complete evidence for investigations or sales data.

Deprecated cache lookup

Returns only the most recent limit entries from the per-host best-effort index populated by /v1/dns/all lookups, with apex deduplication enabled by default.

Not internet-wide

This endpoint does not crawl DNS, zone files, or a complete passive DNS corpus.

Legacy signal

Use results as optional context, not as complete evidence for investigations or sales data.

Deprecated cache lookup

Returns only the most recent limit entries from the per-host best-effort index populated by /v1/dns/all lookups, with apex deduplication enabled by default.

Legacy signal

Use results as optional context, not as complete evidence for investigations or sales data.

Example Request

GET /v1/reverse/mx bash
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/reverse/mx?mx=aspmx.l.google.com"

Example Response

200 OK json
{
  "query": {
    "mx": "aspmx.l.google.com",
    "match": "exact",
    "include_apex_only": true
  },
  "deprecated": true,
  "deprecation_notice": "This endpoint is deprecated. It only searches a best-effort seven-day passive index populated by prior /v1/dns/all lookups and capped at 10,000 recent entries per key. It is not an internet-wide reverse DNS dataset.",
  "results": [],
  "summary": {
    "total_found": 0,
    "returned": 0
  },
  "freshness_summary": {
    "source": "passive_dns",
    "cache_status": "passive_cache_only",
    "result_count": 0,
    "returned_count": 0,
    "apex_domain_count": 0,
    "apex_deduped_count": 0,
    "warning_count": 2,
    "warnings": ["passive_cache_only", "no_cached_matches"],
    "last_seen_span_days": null
  },
  "page": {
    "limit": 100,
    "next_cursor": null
  },
  "meta": {
    "source": "passive_dns",
    "note": "Best-effort seven-day index populated only by prior /v1/dns/all lookups"
  },
  "cache": {
    "hit": null,
    "age_s": null,
    "ttl_s": null,
    "key": null
  }
}

Frequently Asked Questions

What is an MX record?

MX (Mail Exchanger) records specify which mail servers receive email for a domain. They include a priority value and server hostname.

How do you find domains by MX?

Deprecated: this endpoint performs exact-hostname searches only against a best-effort seven-day index populated by prior /v1/dns/all lookups. Each MX host keeps at most 10,000 recent entries. The API evaluates limit entries before returning one row per apex by default, and it is not an internet-wide dataset.

Why use reverse MX lookup?

Use results as optional context, not as complete evidence for investigations or sales data.

How current is the data?

The best-effort index is populated only by /v1/dns/all lookups, refreshes observations for seven days, and caps each MX host at 10,000 recent entries. Missing or failed writes can create gaps.

Related Tools & Resources

HTTP Status Codes

We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Server Error 500

Internal error

Bad Gateway 502

Upstream RDAP error

Service Unavailable 503

Upstream service unavailable or temporarily rate limited.

Gateway Timeout 504

Upstream lookup timed out.

View Deprecated Reverse MX Lookup