跳转到安全报告
分析仪表盘
域安全和威胁情报
oasghj.com favicon

oasghj.com

“Suspected Phishing | Cloudflare”

注册商
Cloudflare
Resolved IP
172.67.188.193
PhishDestroy assessment 关键
可用性 内容不可用 最新观察中的内容不可用 观察到 · HTTP probe
风险信号
病毒检测总数：13/89 自动品牌标签：Cloudflare Google Safe Browsing: threat flag recorded
OTX: 4 refs 2026年9月3日 CDN
API
该域名已被标记为恶意域名
安全引擎报告检测：13。 请格外小心——不要输入凭据或个人信息。
VirusTotal
13 / 89
engine detections
Google Safe Browsing
已标记
OTX
4
community references
报告概览

冒充 Cloudflare: oasghj.com — 内容不可用. 证据摘要: VirusTotal 13/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); Google Safe Browsing…

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

Source evidenceVirusTotal 13 / 89 · Google Safe Browsing: flagged · OTX 4 references 4 sources

VirusTotal

13 / 89 engine detections

打开报告

Google Safe Browsing

Threat flag recorded

打开报告

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

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

Analysis

关键
VirusTotal
13 / 89
OTX
4 community refs
Source results Registration record

PhishDestroy threat report

Overview

oasghj.com is a phishing domain that dressed itself up as Cloudflare, the network and security service used by millions of websites. It targeted Cloudflare account holders and ordinary visitors who trust Cloudflare's branding. PhishDestroy first saw it on 2026-09-03. The site went offline on 2026-09-14, and its DNS was still inactive at the last check on 2026-10-19.

How the scam works

Fake Cloudflare pages exploit a brand people see every day, such as security checks, "verify you are human" screens and account dashboards. Victims are pushed to sign in, confirm details or follow on-screen instructions. Anything typed goes to the operator, and a stolen Cloudflare login can hand over control of a victim's domains, DNS and websites. The page carried the title "Suspected Phishing | Cloudflare," which matches the wording of Cloudflare's own phishing warning page, while PhishDestroy classified the domain as an impersonation of Cloudflare.

Evidence

On 2026-09-15, 13 of 89 VirusTotal engines flagged the domain. They include Google Safe Browsing, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, CRDF, Gridinsoft and alphaMountain.ai. That is a modest share, but it spans independent vendors with different detection methods. Google Safe Browsing separately lists it under SOCIAL_ENGINEERING, its category for deceptive pages that manipulate users. The domain also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.

Infrastructure

The domain was registered through Cloudflare, Inc. and resolved to 172.67.188.193 on Cloudflare's network, geolocated to Canada. Its TLS certificate came from Google Trust Services (WE1), a free and automated issuer, so the padlock in the browser said nothing about who ran the page. The site lasted about eleven days after PhishDestroy first saw it before it went dark.

What to do

If you entered a Cloudflare email and password on this page, change the password right away, enable or reset two-factor authentication, and revoke any API tokens you did not create. Then check your Cloudflare account for unfamiliar DNS records, new members or changed nameservers on your domains. Reuse of that password anywhere else means changing it there too. Defenders should block the domain and the Cloudflare-themed lure pattern, and search proxy and email logs for visits to it between 2026-09-03 and 2026-09-14.

Useful links

VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

域名
Google Safe Browsing 已标记 Social engineering checked 2026年9月15日
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags 2026-09activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 Cloudflare US(US)
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询oasghj.com 的 ICANN RDAP →
首次不可用所需时间 11 days
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年9月3日
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP 声誉不属于此域。

域名服务器 1

  • gerald.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Google Trust Services / WE1
Valid from
2026-09-01 18:37:47
Valid until
2026-11-30 19:36:22
Validity
Within stored validity dates
Collection time
2026-09-15 01:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6bdf844fd7e4ea38ea69f7c57a4a8f4c8a1a5095d3f4a153f7d6c2697806ddd9

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

viewdns.info · 172.67.188.193rapiddns.io

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS 非活动 reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 未知 Probe Inconclusive 20% 2026-10-19 01:14:39 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-09-15 22:18:05 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-15 22:18:05 UTC → 2026-09-30 16:14:55 UTC · 353.95h midpoint estimate ≈ 2026-09-23 07:16:30 UTC · precision low · basis bounded
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.
技术 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

13 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
卡巴斯基
Lionic
PhishFort
SOCRadar
Sophos
网站性能分析

Google PageSpeed Insights — mobile performance audit of oasghj.com · checked Sep 14, 2026

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

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
Low

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

Stored observation history15

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

    未知→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

Earlier observations 10
  1. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    不可用→可访问

  7. VirusTotal · Detection count

    2→13

  8. Availability monitor · Recorded state

    可访问→不可用

  9. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  10. Availability monitor · First collection record

    可访问

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. VirusTotal

    13/89 engine detections

    View source
  4. Added to PhishDestroy

    oasghj.com

    View source

仿冒域名

已存储 142 个仿冒域名

c.loudflare.com subdomain claudflare.com vowel-swap cloadflare.com vowel-swap cloduflare.com transposition cloodflare.com vowel-swap clou.dflare.com subdomain cloudf.lare.com subdomain cloudfalre.com transposition cloudfla.re.com subdomain cloudflaer.com transposition cloudflarecom.com various cloudflore.com vowel-swap
显示全部（88）
cloudflrae.com transposition cloudflure.com vowel-swap cloudflwre.com replacement cloudlfare.com transposition cloufdlare.com transposition cluodflare.com transposition coludflare.com transposition c1oudf1are.com homoglyph c1oudflare.com homoglyph ccloudflare.com repetition cioudfiare.com homoglyph cioudflare.com homoglyph ckoudflare.com replacement cl0udfiare.com homoglyph cliudflare.com replacement clludflare.com replacement clo-udflare.com hyphenation clodflare.com omission clohdflare.com replacement cloidflare.com replacement clooudflare.com insertion cloubflare.com homoglyph clouclflare.com homoglyph cloud-flare.com hyphenation cloudcflare.com insertion cloudclare.com replacement clouddflare.com insertion cloudfare.com omission cloudfflare.com insertion cloudfiare.com homoglyph cloudfla1re.com insertion cloudflaare.com repetition cloudflae.com omission cloudflaee.com replacement cloudflar.com omission cloudflarr.com replacement cloudflarre.com repetition cloudflarz.com replacement cloudflate.com replacement cloudfllare.com repetition cloudflre.com omission cloudflsre.com replacement cloudiflare.com homoglyph cloudlare.com omission cloudlflare.com homoglyph cloudsflare.com insertion cloudtflare.com insertion cloudtlare.com replacement cloudvflare.com insertion cloudxflare.com insertion cloufflare.com bitsquatting clouflare.com omission cloulflare.com bitsquatting clourflare.com replacement clousflare.com replacement cloutflare.com bitsquatting clouudflare.com repetition clowdflare.com bitsquatting cloydflare.com replacement clpudflare.com replacement cludflare.com omission cmoudflare.com bitsquatting cnoudflare.com bitsquatting coudflare.com omission dloudflare.com homoglyph doudflare.com homoglyph gloudflare.com bitsquatting kloudflare.com bitsquatting loudflare.com omission sloudflare.com bitsquatting xn--clodflare-is7d.com homoglyph xn--cloudflae-7fe.com homoglyph xn--cloudflae-7n6d.com homoglyph xn--cloudflar-3f7d.com homoglyph xn--cloudflar-j4a.com homoglyph xn--cloudflre-676d.com homoglyph xn--clouflare-t05d.com homoglyph xn--cludflare-6x3d.com homoglyph xn--cludflare-ml7d.com homoglyph xn--coudflare-0sb.com homoglyph aloudflare.com bitsquatting bloudflare.com bitsquatting cdoudflare.com bitsquatting choudflare.com bitsquatting clgudflare.com bitsquatting clkudflare.com bitsquatting clmudflare.com bitsquatting clnudflare.com bitsquatting

显示 142 个中的 100 个

社区情报

1 条社区报告

类别PHISHING

The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-03T11:07:34.224Z.

Check for cloaking

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

oasghj.com

证据与外部报告

证券分析
VirusTotal 13 det. ChainPatrol ChainAbuse 1 report URLQuery Google SB 已标记 SSL 实验室 CF雷达 恶意 OTX 4 refs WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
Third-Party Detection — ChainAbuse
1 report filed for oasghj.com · category: Phishing · source checked
Flagged by PhishFort Detection System on Sep 3, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
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 反向链接
深度分析
深度分析
Help & reporting

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

2 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.

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

Immediate steps Find reporting contacts

Official reporting routes

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

向当地主管部门报告

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

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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的（包括 oasghj.com)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

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

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

  • 联邦调查局（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

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

实时威胁动态 对该列表提出异议
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

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

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