Mmcp.market

Domain History Contact OSINT - Previous Owner + WHOIS History MCP server

by AnshumanAtrey·io.github.AnshumanAtrey/domain-history-contact-osint·v1.0.19

Domain History Lookup - WHOIS History + Past Owner Contacts

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Domain History Contact OSINT - Previous Owner + WHOIS History yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Domain History Contact OSINT - Previous Owner + WHOIS History tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 6ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Domain History Contact OSINT - Previous Owner + WHOIS History repository's README, as published. We do not edit it. Read it on GitHub

Domain History Contact OSINT - Previous Owner + WHOIS History

Domain history and previous owner lookup for dead, expired and parked domains. WHOIS history, Wayback Machine pages, and the owner's emails, phones, people and organisations, each with a source URL and capture date.

Available as an Apify Actor. $0.25 per domain scan + $0.02 per contact found. One input field, no API key needed.

What does it do?

You type a domain and press Start. You get who owned it and how to reach them, even when the website is gone, as a table where every row carries the URL and capture date it came from. It reads 14 public sources, works on domains that no longer resolve, and always finishes with a report that says which sources answered and which did not.

  • Contacts with provenance. Emails, phones, people and organisations. One dataset row per contact per source, each with sourceUrl, snapshotTimestamp, replayUrl and extractionMethod. One row is one claim you can cite.
  • People and organisations, with roles. A multilingual named-entity model reads the rendered archived pages. Each person carries a role when the page stated one ("Founder", "Geschäftsführer"), a worksFor when a company sat next to the name, a relation flag (site = part of the site itself, mention = named in its content) and the visible snippet the name was read from.
  • Registration. RDAP registrant and organisation where not redacted, registrar, the registrar abuse contact, creation and expiry events, nameservers. WHOIS history back to 2008 with a free SecurityTrails key, or from 2012 with a Whoxy key: pre-GDPR registrant names, emails and phones.
  • DNS now and then. Current A, AAAA, MX, NS, TXT and SOA, historical nameservers and historical IPs from passive DNS, each IP geolocated to country, city, ISP and AS number. SaaS verification tokens in TXT are flagged because they tie a domain to named vendors.
  • Certificate history. Every hostname that ever appeared in a certificate for the domain. Certificates outlive domains.
  • Past versions of the website. Archived pages sampled across the domain's whole lifetime and weighted toward contact, about, team, imprint, careers, management and board pages.
  • Server software. The dead origin's own response headers, recovered from the archive. From a domain offline for years: Apache/1.3.36 (Unix) ... PHP/4.4.2 FrontPage/5.0.2.2635 mod_ssl/2.8.27 OpenSSL/0.9.7a.
  • Tracking IDs. Google Analytics, GTM, AdSense, Google Ads, Segment, Optimizely, Hotjar, Mixpanel and Meta pixel IDs from the archived bytes. Reverse-look these up to find every other domain the same owner ran.
  • Inbound references. Who else mentioned this domain: urlscan.io submissions, Arquivo.pt full-text archive hits, Common Crawl, and public source code on grep.app. Config files and mail settings name real addresses.
  • A per-source coverage report. Which sources answered, which held nothing, and which throttled you. Throttled is reported as unknown, not as empty.

How is it different from a contact scraper or a WHOIS history service?

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

claude mcp add --transport http domain-history-contact-osint https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint
Add to Cursor

Domain History Contact OSINT - Previous Owner + WHOIS History: common questions

Is Domain History Contact OSINT - Previous Owner + WHOIS History MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Domain History Contact OSINT - Previous Owner + WHOIS History safety report
How do I install Domain History Contact OSINT - Previous Owner + WHOIS History?
It runs remotely at mcp.apify.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Domain History Contact OSINT - Previous Owner + WHOIS History need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Domain History Contact OSINT - Previous Owner + WHOIS History maintained?
The last commit was in the last day (2026-09-24). The latest release is v1.0.19.
Is Domain History Contact OSINT - Previous Owner + WHOIS History up?
100% of our last 2 checks got an answer. We check remote servers about four times a day.

More from AnshumanAtrey →