跳转到安全报告
域安全和威胁情报
form.payou.cc favicon

form.payou.cc

注册商
NameCheap
Resolved IP
188.114.96.9
Registered
2025年6月14日
PhishDestroy assessment 关键
可用性 可达 · 访问受限 可达响应;页面内容未经验证 观察到 · HTTP probe
病毒检测总数:4/89 自动品牌标签:Google 最后已知的活跃状态
2026年9月9日 CDN
API
该域名已被标记为恶意域名
安全引擎报告检测:4。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
Domain age
报告概览

冒充 Google: form.payou.cc — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 4/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar); PhishDestroy score 71/100.…

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

Source evidenceVirusTotal 4 / 89 4 sources

VirusTotal

4 / 89 engine detections

打开报告

Google Safe Browsing

No threat flag

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

关键
VirusTotal
4 / 89

PhishDestroy threat report

Overview

form.payou.cc is an impersonation phishing page that copies a legitimate service to win visitors' trust and harvest what they type. PhishDestroy first flagged it on 2026-09-09. As of 2026-10-19 the site was still online, with its content reachable but sitting behind a protective challenge screen. Its page title reads "Just a moment...", the wording of a browser-check interstitial rather than branded content, while our analysis classifies the site as impersonation phishing.

How the scam works

Impersonation pages copy the look and wording of a service the victim already uses, then present a login, verification or payment form. Whatever is entered goes straight to the operators, not the real company. The "form." subdomain fits that pattern of a data-collection page. The browser-check screen in front of the content can also make the site look routine and slow down automated scanners. Victims typically lose account credentials, personal details or card and payment information, which are then used for account takeover or resold.

Evidence

Independent detection is thin. On 2026-09-22, VirusTotal showed 4 of 89 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. That low count means most security tools and browsers will not warn users, so a visitor cannot rely on a red warning page to protect them. Among the blocklists we track, PhishDestroy is the only one listing it so far.

Infrastructure

The domain was registered on 2025-06-14 through NameCheap, Inc., roughly fifteen months before we detected the phishing page on it. A domain that sits that long before use can pass reputation checks that would catch a freshly registered name. Traffic runs through Cloudflare, Inc. on an address geolocated to Canada, which masks the actual origin server. That same Cloudflare layer explains the "Just a moment..." challenge visitors see.

What to do

If you entered a password on this site, change it right away on the genuine service and on any other account that shares it. Then turn on or reset two-factor authentication and sign out of all active sessions. If you submitted card or bank details, contact your card issuer to block the card and dispute any unfamiliar charges, and treat follow-up emails or calls about the same account with suspicion. Defenders should block form.payou.cc at DNS, proxy and email gateways. They should also search logs for users who reached it after 2026-09-09 and report it to Cloudflare for abuse handling, since few vendors detect it yet.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

域名
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
Registrar (base domain) NameCheap US(US)
滥用举报联系方式["abuse@namecheap.com"]
ICANN 注册管理机构ICANN Lookup (RDAP) →
Registration (base domain)payou.cc · 创建 2025年6月14日 — Expires 2027年6月14日
HTTP 状态码403 Forbidden
技术详情Provenance & timestamps
首次发现2026年9月9日
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.9
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP 声誉不属于此域。

域名服务器 1

  • olga.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Google Trust Services / WE1
Valid from
2026-09-02 15:38:33
Valid until
2026-12-01 16:36:14
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-16 19:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7f5bf3680472a1c9ace3db4750876ce8288ee29e5c4404a2ac6b756974511bea
Certificate names · 1 SANs
  • payou.cc

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

Latest Classified Outcome 2026-10-19 22:29:18 UTC

Primary outcome Reachable but protected reason: HTTP access restricted 65% confidence
Attribution Cloudflare 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 Cloudflare Access Restriction 65% 2026-10-19 22:29:18 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-19 22:35:32 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.
技术 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

4 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
网站性能分析

Google PageSpeed Insights — mobile performance audit of form.payou.cc · checked Sep 18, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.82s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history16

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

Earlier observations 11
  1. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  2. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  3. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  4. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  5. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  6. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  7. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  8. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  9. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  10. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · Cloudflare · access_restriction

  11. Availability monitor · First collection record

    可访问

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    4/89 engine detections

    View source
  3. Added to PhishDestroy

    form.payou.cc

    View source

社区情报

1 条社区报告

类别FAKE_PROJECT

Fake online casino platform (dragonara.cc) and payment processing gateways (link80.linkswat.pro, form.payou.cc). They collect deposits via crypto wallets and illegal P2P card transfers, blocking users from withdrawing funds. Crypto wallets used by scams: USDT TRC20: TFj4Am2yXchBr

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

form.payou.cc

证据与外部报告

Community Scam Report — ChainAbuse
1 report filed for form.payou.cc (1 written by a person) · category: Fake Project · source checked
“Fake online casino platform (dragonara.cc) and payment processing gateways (link80.linkswat.pro, form.payou.cc). They collect deposits via crypto wallets and illegal P2P card transfers, blocking users from withdrawing funds. Crypto wallets used by scams: USDT TRC20: TFj4Am2yXchBrr6H6VxkEDwgBzmjBmSyz ETH: 0x6A07092c93be56Bb58d68879a6cfF9BAE2EC70b9 BTC: 3GtmtyzdUpyD89JxA7kjxJKThPxS9MBQX7”
— reported by Anonymous on Sep 9, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
深度分析
Help & reporting

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

1 evidence signal groups linked 0 stored notification records 可达 · 访问受限

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

97个国家目录

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

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

针对受害者的建议与指导

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

我应该立即采取什么措施?

紧急

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • 更改所有密码 — 电子邮件、Exchange 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息?

联邦调查局(FBI)指南

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 form.payou.cc)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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

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

实时威胁动态 对该列表提出异议
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

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

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/form.payou.cc"
  title="PhishDestroy threat report for form.payou.cc"
  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>