MCP servers · anshumanatrey

Domain History Contact OSINT - Previous Owner + WHOIS History

An MCP server that looks up who owned or ran a domain in the past, including offline, expired and parked domains, with each finding tied to a source URL and capture date.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

This MCP server looks up the past and present ownership of a domain, including dead, expired and parked ones. It collects WHOIS history, archived website pages, and the emails, phone numbers, people and organisations found in them, with each row carrying the source URL and capture date. It also covers registration data, current and historical DNS records, certificate history, archived server headers, tracking IDs and inbound references, drawing on 14 public sources. Each run ends with a report stating which sources responded and which did not.

It suits cases where a domain's website no longer exists but someone still needs to know who was behind it. Examples include checking a supplier or counterparty whose site has vanished, or investigating fraud where every finding must carry a citable source and date. Each contact row stands alone as a single sourced claim, which makes the results easy to reference in a report.

To use it, connect an MCP client such as Claude, Claude Code, Codex or another compatible client to Apify, then enter a domain as the single input. Scans are billed per domain and per contact found. Extended WHOIS history requires a free SecurityTrails key or a Whoxy key.

Limitations and requirements

Requires signing in to Apify. Pricing is $0.25 per domain scan, $0.02 per contact found and $0.002 per mention. WHOIS history back to 2008 needs a free SecurityTrails API key; history from 2012 needs a Whoxy API key. Sources that throttle requests are reported as unknown, not as empty. Current WHOIS registrant data is redacted for most domains since GDPR in 2018.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source
    Domain History Contact OSINT - Previous Owner + WHOIS History

    Domain History Lookup - WHOIS History + Past Owner Contacts

    v1.0.27
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
Domain History Contact OSINT - Previous Owner + WHOIS History | AI Gate Discover