跳转到安全报告
分析仪表盘
域安全和威胁情报
parik24-ua.io favicon

parik24-ua.io

“Suspected Phishing | Cloudflare”

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

parik24-ua.io — 可达 · 访问受限 (HTTP 403). 品牌冒充：Cloudflare; 诈骗类型：Impersonation. 证据摘要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet); Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 98/100. 注册商: Namecheap.

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

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
12 det.
OTX references
4 community refs
CF雷达
恶意
URLScan
URLScan
报告 ↗
TLS 证书
已过期或未验证
年龄
9 mo
观测状态
可达 · 访问受限 403
PhishDestroy
DestroyList
已列入

Source evidence

7 sources

VirusTotal

12 / 89

报告

CF雷达

provider verdict: malicious

报告

Spamhaus DBL

DBL_PHISH

OTX

4 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
12/89
OTX
4 community refs
URLScan
Stored capture

Assessment

parik24-ua.io returned HTTP status 403 in an HTTP check dated 2026-10-01, a recorded response rather than a statement about all content. The domain was first observed on 2026-09-18, and a PhishDestroy internal listing is recorded as true.

Recorded Evidence

VirusTotal recorded 12 detections across 89 scanners on 2026-09-19, and OTX recorded 4 pulses on the same date. The HTTP check on 2026-10-01 returned status 403, while the PageSpeed check on 2026-09-18 produced a performance score of 88. Registration occurred on 2026-01-08 with NAMECHEAP INC, and the SSL certificate was issued by Let's Encrypt / YE2 and scanned on 2026-09-18.

Interpretation

The VirusTotal and OTX records offer two separate views of how security tooling characterized parik24-ua.io, while the PhishDestroy listing reflects a publisher catalogue entry. The HTTP 403 response describes only the reply recorded on that date, and the PageSpeed score addresses measured performance rather than safety. Because the source dates span 2026-09-18 through 2026-10-01, readers can compare the observations chronologically without treating them as a single measurement.

Recommended Actions

Preserve the VirusTotal and OTX records for parik24-ua.io so later comparisons use the same source values. Separately retain the PhishDestroy listing entry and the HTTP response record, and compare each against future checks of parik24-ua.io. Review the PageSpeed result alongside the other records when assessing what the collected sources show.

探测与规避分析

隐身和流量分配检查

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

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

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

扫描说明: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

扫描期间服务提供商的响应: cloudflare_phishing_interstitial

TDS指纹识别实时演示
七个Keitaro指纹，外加爬虫与浏览器的对比，当此面板打开时，由PhishDestroy扫描器运行。
等待

已保存的截图 · 2 captures

Primary capture 1 / 2
来源Primary capture
Recorded2026-09-18 08:24 UTC
StateStored capture
Position1 / 2
Open capture Wayback 下载

Domain details

域名
URLScan Verdict 分析完成 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX Tags 2026-09activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 Namecheap US(US)
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询parik24-ua.io 的 ICANN RDAP →
注册信息创建 2026年1月8日 (278d) — Expires 2027年1月8日
HTTP 状态码403 Forbidden
Elapsed Since First Report 2h
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 可达 · 访问受限.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年9月18日
DOM Analysisanalyzed 2026年9月18日score 98/1001 brand signal
Submitted URLhttps://parik24-ua.io/
Favicon Hash
页面标题
Suspected Phishing | Cloudflare
Impersonates
Cloudflare
TLS 证书
Hostname coverage not recorded · 颁发者 Let's Encrypt / YE2 · stored validity ends in 31 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP 声誉不属于此域。

域名服务器 2

  • harley.ns.cloudflare.com
  • liberty.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YE2
Valid from
2026-08-16 13:21:33
Valid until
2026-11-14 13:21:32
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-09-18 10:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintaff89bcce0fc7ba5069b67a5daa6c26e9cd6eaaecf19c68b6caca773672f0e99

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

viewdns.info · 104.21.92.71rapiddns.io

Latest Classified Outcome 2026-10-13 01:30:00 UTC

Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Resolved Registration: Unknown
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-10-13 01:30:00 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-09-18 08:24:54 UTC current episode first observed: 2026-10-01 01:52:48 UTC observed RIP window: 2026-09-18 08:24:54 UTC → 2026-10-01 01:52:48 UTC · 305.46h midpoint estimate ≈ 2026-09-24 17:08:51 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.
技术 · 8 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

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

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of parik24-ua.io · checked Sep 18, 2026

88
Needs Work
Performance
FCP
1.22s
First Contentful Paint
LCP
3.26s
Largest Contentful Paint
CLS
0.025
Cumulative Layout Shift
TBT
15ms
Total Blocking Time
SI
5.73s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

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-09-18 11:03:51 UTC
    Domain state transitioned from alive to dead.
  2. VirusTotal Detections Update 2026-09-18 10:29:56 UTC
    VirusTotal scanner detections updated from 11 to 12. Added scanner alerts: SOCRadar.
  3. Threat First Observed 2026-09-18 08:24:54 UTC
    Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.92.71.

威胁响应 Pipeline

发现
Analysis
Monitoring

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

已捕获威胁
parik24-ua.io 已检测到并排入队，待进行全面分析
2026年9月18日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年9月18日
URLScan.io Capture
已存储 URLScan report with capture artifacts
2026年9月18日
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
2026年9月23日
VirusTotal
12/89 recorded on VirusTotal
2026年9月19日
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年9月19日
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of Cloudflare
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
2026年9月18日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月14日
Content Observed Unavailable
监控记录了一个不可用的响应 (HTTP 403)；原因尚未独立确定。
2026年9月18日
VT Detection +1
+1 new detection (11 → 12): SOCRadar
2026年9月18日
DestroyList 已发布
Listed in the public PhishDestroy/DestroyList repository
2026年9月18日
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

仿冒域名

已存储 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 个

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 12 det. ChainPatrol URLQuery SSL 实验室 Hostname coverage not recorded CF雷达 恶意 OTX 4 refs 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 Archived
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析

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

4 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/parik24-ua.io"
  title="PhishDestroy threat report for parik24-ua.io"
  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>