原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Domain History Contact OSINT - Previous Owner + WHOIS History

作者:AnshumanAtrey版本 1.0.27i★ 0i在云端运行官方网站 ↗
注册名称io.github.AnshumanAtrey/domain-history-contact-osint

安装方法

能做什么

Domain History Lookup - WHOIS History + Past Owner Contacts

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 需要 Authorization
  • 分类 网络安全

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Domain History Contact OSINT - Previous Owner + WHOIS History。按照 https://mcp.popnx.com/i/anshumanatrey-domain-history-contact-osint.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.apify.com) · ✓ 命令已检查 2026年11月20日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 5 分钟

需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 注册并创建 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Domain History Contact OSINT - Previous Owner + WHOIS History 网站 ↗

  2. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Domain History Contact OSINT - Previous Owner + WHOIS History
    Remote MCP server URL · 地址https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint

    在 Request headers 下添加这个名称和值

    Header 名称Authorization
    值Bearer <在这里粘贴你的密钥>

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  4. 在聊天中开启

    +ConnectorsDomain History Contact OSINT - Previous Owner + WHOIS History

  5. 试一试

    用 Domain History Contact OSINT - Previous Owner + WHOIS History 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Domain History Contact OSINT - Previous Owner + WHOIS History,或回答中出现 Domain History Contact OSINT - Previous Owner + WHOIS History 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Domain History Contact OSINT - Previous Owner + WHOIS History

Domain History Contact OSINT - Previous Owner + WHOIS History 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式

你可以改用这些方式

A · 使用能连接 Domain History Contact OSINT - Previous Owner + WHOIS History 的应用

  • 需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
  • 需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建)
  • 需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建)
  • 需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建)

B · 网络安全 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code · 约 5 分钟

需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建)

  1. 注册并创建 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Domain History Contact OSINT - Previous Owner + WHOIS History 网站 ↗

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user domain-history-contact-osint 'https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint' --header 'Authorization: Bearer your-value'

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Claude Code 中输入 /mcp

    应能看到 Domain History Contact OSINT - Previous Owner + WHOIS History 在列表中并显示已连接

  5. 试一试

    用 Domain History Contact OSINT - Previous Owner + WHOIS History 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Domain History Contact OSINT - Previous Owner + WHOIS History,或回答中出现 Domain History Contact OSINT - Previous Owner + WHOIS History 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 5 分钟

需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建)

  1. 注册并创建 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Domain History Contact OSINT - Previous Owner + WHOIS History 网站 ↗

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Domain History Contact OSINT - Previous Owner + WHOIS History 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Cursor 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Domain History Contact OSINT - Previous Owner + WHOIS History 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Domain History Contact OSINT - Previous Owner + WHOIS History,或回答中出现 Domain History Contact OSINT - Previous Owner + WHOIS History 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 5 分钟

需要 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥(在开发者网站创建)

  1. 注册并创建 Domain History Contact OSINT - Previous Owner + WHOIS History 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Domain History Contact OSINT - Previous Owner + WHOIS History 网站 ↗

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Domain History Contact OSINT - Previous Owner + WHOIS History 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 VS Code 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Domain History Contact OSINT - Previous Owner + WHOIS History 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Domain History Contact OSINT - Previous Owner + WHOIS History,或回答中出现 Domain History Contact OSINT - Previous Owner + WHOIS History 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Domain History Contact OSINT - Previous Owner + WHOIS History 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user domain-history-contact-osint 'https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint' --header 'Authorization: Bearer your-value'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "domain-history-contact-osint": {
      "url": "https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "domain-history-contact-osint": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=anshumanatrey/domain-history-contact-osint",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

需要你填写的值

  • Authorization 机密 必填 HTTP header
    Apify API 令牌,格式为 'Bearer '。运行费用将计入该账户。
    查看英文原文Apify API token, as 'Bearer '. Runs bill to this account.

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.0.27
发布到注册中心i
2026年11月18日
代码最后更新i
2026年11月16日
最近检查
2026年11月17日
作者
AnshumanAtrey
网站
apify.com
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 AnshumanAtrey 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于4天前

  • ✓ 通过

    有许可证

    使用 MIT

  • ✓ 通过

    端点有响应

    在 345 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/anshumanatrey-domain-history-contact-osint.svg)](https://mcp.popnx.com/en/servers/anshumanatrey-domain-history-contact-osint)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“网络安全”中的其他服务器比较i

  • 星标数多于此分类中其他 1124 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1124 个服务器的 92% 更新
  • 基础检查结果等于或优于此分类中其他 1124 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Domain History Contact OSINT - Previous Owner + WHOIS History 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:Authorization

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于4天前,最新版本(1.0.27)于前天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:GitHits, Dependency Management MCP Server, Snyk MCP, TokenSafe, Draugr

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHits

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

作者:githits-com正在增长↓ 3807/周★ 138昨天更新

电脑或云端✓ 服务方 · githits.com

Snyk MCP

Easily find and fix security issues in your applications leveraging Snyk platform capabilities.

作者:snyk广泛使用↓ 76.2万/周★ 617个月前更新

在你的电脑上运行✓ 服务方 · snyk.io

TokenSafe

Your AI agent is smart enough to code all day. Local firewall & zero-loss runtime.

作者:tokensafe-dev广泛使用↓ 6785/周★ 47今天更新

电脑或云端✓ 服务方 · tokensafe.dev

Draugr

Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.

作者:draugr-dev起步阶段★ 303天前更新

在你的电脑上运行✓ 服务方 · draugr.dev
与相似项目对比
本项
Domain History Contact OSINT - Previous Owner + WHOIS History
GitHitsDependency Management MCP ServerSnyk MCPTokenSafeDraugr
运行位置在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装需要安装在电脑上云端或安装在电脑上都可以需要安装在电脑上
需要密钥是否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/55/53/43/35/53/3
许可证MITApache-2.0–Apache-2.0MITApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Domain History Contact OSINT - Previous Owner + WHOIS History

This repo is the public home of the Domain History Contact OSINT - Previous Owner + WHOIS History actor on Apify: its docs, API examples in examples/, MCP setup and issues. The actor runs on Apify; its source code is private.

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.


Use it from an AI assistant:

  • Claude (claude.ai and the desktop app): Add Domain History Contact OSINT to Claude, click Continue, sign in to Apify, Allow, and ask in plain words.
  • Claude Code: claude mcp add --transport http domain-history-contact-osint "https://mcp.apify.com?tools=anshumanatrey/domain-history-contact-osint", then run /mcp to sign in to Apify.
  • Codex: codex mcp add domain-history-contact-osint --url "https://mcp.apify.com?tools=anshumanatrey/domain-history-contact-osint", then codex mcp login domain-history-contact-osint.
  • Any other MCP client: https://mcp.apify.com?tools=anshumanatrey/domain-history-contact-osint, signed in with Apify or an Authorization: Bearer header.

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?

This actorContact scrapers on ApifyWayback-only toolsWHOIS history services
Works when the site is offlineYesNoYesRecords only
Source URL and capture date on every contactYes, on every rowNo, flat arraysOne URL per valueNot applicable
Named people with job titlesYesNoNoRegistrant only, mostly redacted since 2018
Registration, certificates, passive DNS, public codeYesNoNoWHOIS only
Price$0.25 per scan + $0.02 per contact, $0.002 per mentionAbout $0.002 per page$0.0035 per snapshot$2 per 1,000 lookups (Whoxy) up to enterprise contracts (DomainTools)
SetupNoneNonepip or self-host for the open-source onesAccount and credits

Three measurements behind that table. On one dropped domain the archived contact page held 0 addresses, while certificate transparency returned 2,644 certificates and public code search returned 3 genuine addresses: the extra sources are where dead domains still answer. The largest contact scraper on the Store (58,952 users) returns a flat array of pages next to a flat array of emails with no mapping between them, which looks like provenance and is not. And since GDPR in 2018, the registrant on current WHOIS is redacted for most domains, so a named owner comes from archived pages, certificates and WHOIS history, not from today's record.

Two open-source tools deserve a mention. WayTrace and kronikier both mine web archives for historical contacts and both are MIT. If archives are all you need, use them. This actor exists for the case where the archive is thin and you still need an answer, which is the normal case on a fully dropped domain.

When should I use it?

  • You need to find out who owned a domain in the past, or who ran a website that is now offline.
  • A counterparty, supplier or "company" you are checking has a website that has vanished, been scrubbed or been parked, and you need the people behind it.
  • You are investigating fraud, a scam or financial crime and every finding must carry a source URL and date you can put in a report.
  • You are buying an expired domain and want to know what it used to be, who ran it, and which analytics IDs tie it to other sites.
  • You are a journalist or in legal discovery and need the Wayback Machine mined for emails and phone numbers with the capture date on each hit.
  • You want to contact the previous owner of a domain, for a purchase, a takedown, or a transfer.

What does it cost?

Pay-per-event. You pay for the scan and for what it finds; platform compute is included.

EventPriceWhen it fires
Domain scan$0.125 per GB of run memory, so $0.25 at the default 2 GBOnce per domain, at any depth. Covers the archive crawl, page rendering, the entity model, registration, DNS, certificate and reference lookups, and the coverage report
Contact with source$0.02Per row that identifies someone: an email, a phone number, a person or organisation that is part of the site, or a registrant detail from WHOIS history, certificates or public code
Mention$0.002Per row naming a person or organisation that only appears in the site's content, such as a company in a biography. A tenth of a contact, kept for context

On paid Apify plans the contact and mention prices are 10% less on Scale ($0.018 and $0.0018) and 20% less on Business and above ($0.016 and $0.0016); the domain scan fee is the same on every plan.

The summary row is free.

Typical scan costs

Row counts measured on the platform at Standard depth (Quick, the default, finds most of the same contacts from fewer pages); prices at the default 2 GB:

  • Small dead site (youthgrowyouth.in): 6 contacts + 36 mentions, $0.44
  • Sparse result (yikyakapp.com): 3 contacts, no mentions, $0.31
  • Large corporate archive (theranos.com, 231 rows): 47 contacts + 183 mentions, $1.56
  • Nothing recoverable: $0.25, the scan plus the free summary row that says why

A Quick run takes about 3 minutes at 2 GB and Standard about 6; raising memory to 4 GB roughly halves the time and doubles the scan fee. Deep depends on how much the archive holds. Set a spending limit on the run for a hard cap; the summary row says so if it was reached. A run also always finishes inside its own timeout: when the timeout comes before the scan is done, the report is written with what was read and says which pages and sources were left, as unknown rather than absent. Raise the timeout under Run options to read the rest.

Which inputs does it take?

FieldRequiredWhat it does
domainsYesOne domain, or several, one per line. Full URLs and www. are cleaned automatically
depthNoquick (about 30 archived pages, about 3 minutes, the default), standard (about 120), deep (up to 500)
sectionsNoWhich of the 8 report sections to build. All are ticked by default. Unticking "Saved copies of the old website" makes the run about 10x faster
securityTrailsApiKeyNoDated DNS history and WHOIS history back to 2008. Free tier: 2,500 queries a month, no card
whoisHistoryApiKeyNoWhoxy WHOIS history from 2012 at $0.005 per lookup. Pre-GDPR registrant names, emails and phones

What does the output look like?

Each dataset record is one contact from one source. A person row from a real run, with the sightings array cut to one entry:

{

"domain": "youthgrowyouth.in", "type": "person", "value": "Anshuman Atrey", "role": null, "worksFor": "Youth Grow Youth", "relation": "site", "pagesSeenOn": 14, "confidence": "high", "sourceType": "wayback", "sourceUrl": "https://youthgrowyouth.in/businesses/", "snapshotTimestamp": "20230605184117", "replayUrl": "https://web.archive.org/web/20230605184117id_/https://youthgrowyouth.in/businesses/", "extractionMethod": "ner", "occurrences": 40, "firstSeen": "20230605184117", "lastSeen": "20240328173211", "snippet": "Copyright © 2023 Youth Grow Youth | Created with ❤ by Anshuman Atrey", "sightings": [ { "sourceType": "wayback", "sourceUrl": "https://youthgrowyouth.in/businesses/", "snapshotTimestamp": "20230605184117", "replayUrl": "https://web.archive.org/web/20230605184117id_/https://youthgrowyouth.in/businesses/", "extractionMethod": "ner", "pageId": 1, "context": { "role": null, "worksFor": "Youth Grow Youth", "snippet": "Copyright © 2023 Youth Grow Youth | Created with ❤ by Anshuman Atrey" } } ] }

An email row. This address was hidden behind Cloudflare's email obfuscation on the page and decoded:

{

"domain": "youthgrowyouth.in", "type": "email", "value": "mail@youthgrowyouth.in", "confidence": "medium", "sourceType": "wayback", "sourceUrl": "https://youthgrowyouth.in/businesses/", "snapshotTimestamp": "20230605184117", "rep

只显示了开头部分;其余内容请在仓库中阅读