跳转到安全报告
分析仪表盘
域安全和威胁情报
exodus-wallet-faq.created.app favicon

exodus-wallet-faq.created.app

“404: This page could not be found.”

注册商
Name.com
Resolved IP
216.150.16.65
Registered
2023年7月12日
威胁判定 关键
可用性 可达 · 访问受限 可达响应；页面内容未经验证 观察到
Source: HTTP probe
风险信号
病毒检测总数：16/89 品牌冒充：Exodus 最后已知的活跃状态
2026年9月4日 Exodus CDN
API
该域名已被标记为恶意域名
安全引擎报告检测：16。 请格外小心——不要输入凭据或个人信息。
报告概览

exodus-wallet-faq.created.app — 可达 · 访问受限 (HTTP 403). 品牌冒充：Exodus; 诈骗类型：Impersonation. 证据摘要: VirusTotal 16/89 (Criminal IP, alphaMountain.ai, Chong Lua Dao, CyRadar, ESET); CF Radar malicious; PhishDestroy score 95/100. 注册商: Name.com.

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

VirusTotal
VirusTotal
16 det.
CF雷达
恶意
URLScan
URLScan
报告 ↗
TLS 证书
已过期或未验证
年龄
3.3 yr
观测状态
可达 · 访问受限 403
PhishDestroy
DestroyList
已列入

Source evidence

6 sources

VirusTotal

16 / 89

报告

CF雷达

provider verdict: malicious

报告

OTX

no community references

报告

URLScan capture

存储的报告

Stored URLScan capture preview
报告

URLScan verdict

分析完成

报告

Google Safe Browsing

Checked; no threat flag recorded

报告
网络安全情报
CF Cloudflare Radar Verdict 恶意
Phishing
View full Cloudflare Radar report

证据摘要

关键
VirusTotal
16/89
URLScan
Stored capture

Assessment

exodus-wallet-faq.created.app returned HTTP 404 in a check recorded on 2026-10-01, and the domain was first observed on 2026-09-04. A PhishDestroy internal listing also records the domain in its catalogue.

Recorded Evidence

The HTTP check on 2026-10-01 recorded status 404 for exodus-wallet-faq.created.app. The domain was first observed on 2026-09-04, and the PhishDestroy internal listing records it in that catalogue. VirusTotal, checked on 2026-09-16, reported 16 detections across 89 scanners. The IP address 216.150.16.65 is recorded with country US and organization Vercel, Inc.

Interpretation

The recorded HTTP response describes only the single request made on its check date, not all content that may exist on the domain. The first-observed date and the VirusTotal check date fall on different days, so the two records describe separate points in time rather than a single measurement. The PhishDestroy listing and the VirusTotal detection count are separate source records, and their values should be read as separate observations rather than combined into one conclusion.

Recommended Actions

Reviewers should preserve the PhishDestroy internal listing and the VirusTotal record for exodus-wallet-faq.created.app as separate source records. They should compare the recorded HTTP status with the VirusTotal detection count in later checks to see whether the two records continue to describe the same domain. Any future review of exodus-wallet-faq.created.app should keep the first-observed record alongside the later checks so the timeline remains traceable.

探测与规避分析

疑似隐藏内容：扫描器显示的标题与访问者看到的标题不一致

尚未扫描 目前尚未记录到爬虫与浏览器之间的差异

针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。

存储的隐身标志
尚未扫描
上次隐形扫描
扫描器检测到的服务器头信息
Vercel

扫描说明: alive_content: raw=content_403; http=403; via=https_direct; server=Vercel

显示给安检仪的标题Vercel Security Checkpoint
向浏览器访问者显示的标题404: This page could not be found.
TDS指纹识别实时演示
七个Keitaro指纹，外加爬虫与浏览器的对比，当此面板打开时，由PhishDestroy扫描器运行。
等待

已保存的截图 · 2 captures

Primary capture 1 / 2
来源Primary capture
Recorded2026-09-04 18:56 UTC
StateStored capture
Position1 / 2
Open capture Wayback 下载
页面标题
404: This page could not be found.
TLS 证书
Hostname coverage not recorded · 颁发者 Let's Encrypt / YR2 · stored validity ends in 49 days

Domain details

域名
URLScan Verdict 分析完成 score 0 report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP 声誉不属于此域。
Registrar (base domain) Name.com US(US)
滥用举报联系方式["abuse@name.com"]
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询created.app 的 ICANN RDAP →
Registration (base domain)created.app · 创建 2023年7月12日 — Expires 2027年7月12日
HTTP 状态码403 Forbidden
技术详情Provenance & timestamps
首次发现2026年9月4日
DOM Analysisanalyzed 2026年10月9日score 88/100
Favicon Hash
ICANN OVERSIGHT Registration: created.app

认证和 RAA 背景

Registrar accreditation and DNS abuse obligations

For the registrable domain created.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

认证是一纸合同，不是安全印章。 核实 ICANN 费用 阅读 RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.150.16.65
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

Edge-IP 声誉不属于此域。

域名服务器 1

  • ns2.vercel-dns.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YR2
Valid from
2026-09-04 08:43:43
Valid until
2026-12-03 08:43:42
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:28 UTC
Collection source
PhishDestroy collector
Certificate fingerprint939dcd2ea88a9fb0cdc440fbfa55064376759753b259b34a3242d277c46010eb

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 216.150.16.65rapiddns.io

Latest Classified Outcome 2026-10-13 22:06:23 UTC

Primary outcome Reachable but protected reason: HTTP access restricted 50% confidence
Attribution mechanism: Access Restriction source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected HTTP access restricted Access Restriction 50% 2026-10-13 22:06:23 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-13 22:06:23 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 9 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

16 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 16 detections
Criminal IP
alphaMountain.ai
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-10-09 01:25:49 UTC
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-09-14 22:00:21 UTC
    Domain state transitioned from alive to dead.
  3. Threat First Observed 2026-09-14 21:53:13 UTC
    Domain ingestion complete. Initial state is marked as alive.

威胁响应 Pipeline

发现
Analysis
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

已捕获威胁
exodus-wallet-faq.created.app 已检测到并排入队，待进行全面分析
2026年9月4日
URLScan.io Capture
已存储 URLScan report with capture artifacts
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
16/89 recorded on VirusTotal
2026年9月16日
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of Exodus
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月14日
Site Came Back Online
Domain is responding again — monitoring resumed
2026年10月9日
Content Observed Unavailable
监控记录了一个不可用的响应 (HTTP 404)；原因尚未独立确定。
2026年9月15日
DestroyList 已发布
Listed in the public PhishDestroy/DestroyList repository
2026年9月4日
Monitoring Continues
该域仍然可达或访问受限；未来的检查可能会更新这一观察结果。
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web Symantec网站评审 AviraURL reporting Avast / AVGURL reporting 卡巴斯基OpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

仿冒域名

已存储 88 个仿冒域名

esodus.com replacement exadus.com vowel-swap exdous.com transposition exedus.com vowel-swap exidus.com replacement exodas.com vowel-swap exodis.com replacement exodos.com vowel-swap exodsu.com transposition exoduscom.com various exodys.com replacement exosus.com replacement
显示全部（76）
exudus.com vowel-swap ixodus.com vowel-swap oxodus.com vowel-swap 3exodus.com insertion 3xodus.com replacement 4exodus.com insertion axodus.com bitsquatting cxobus.com homoglyph dexodus.com insertion e-xodus.com hyphenation ecodus.com replacement edxodus.com insertion eexodus.com repetition eodus.com omission ex0dus.com homoglyph excodus.com insertion exdus.com omission exo-dus.com hyphenation exobus.com homoglyph exod-us.com hyphenation exoddus.com repetition exodes.com bitsquatting exodeus.com insertion exodius.com homoglyph exodlus.com homoglyph exods.com omission exodts.com bitsquatting exodu.com omission exoduc.com bitsquatting exodus1.com addition exodus2.com addition exodus3.com addition exodus4.com addition exodus5.com addition exodus7.com addition exodus8.com addition exodus9.com addition exodusa.com addition exoduse.com addition exodusk.com addition exodusm.com addition exodusn.com addition exoduso.com addition exoduss.com addition exodust.com addition exodusu.com addition exodusx.com addition exodusz.com addition exodux.com replacement exoduz.com replacement exoduzs.com insertion exodyus.com insertion exolbus.com homoglyph exolus.com bitsquatting exoodus.com repetition exorus.com replacement exotus.com bitsquatting exous.com omission exoxus.com replacement exxodus.com repetition ezodus.com bitsquatting mxodus.com bitsquatting rexodus.com insertion sexodus.com insertion uxodus.com bitsquatting wexodus.com insertion xn--exdus-381b.com homoglyph xn--exdus-t9a.com homoglyph xn--exdus-wua.com homoglyph xn--exods-9d2b.com homoglyph xn--exods-x49a.com homoglyph xn--exodu-ycb.com homoglyph xn--exous-vya.com homoglyph xn--xodus-5za.com homoglyph xodus.com omission zexodus.com insertion

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 16 det. ChainPatrol URLQuery SSL 实验室 Hostname coverage not recorded CF雷达 恶意 WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析

您是否受到本网站的影响？

3 evidence signal groups linked 0 reports recorded 可达 · 访问受限
If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/exodus-wallet-faq.created.app"
  title="PhishDestroy threat report for exodus-wallet-faq.created.app"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>