跳转到安全报告
⚠️
该域名已被标记为恶意域名
安全引擎报告检测:17。 报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 4 months has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
4 months
Reports sent
1
Current status
HTTP 200 at latest stored check
域安全和威胁情报

securexat[.]cc

“SecureX AT”

威胁判定 关键 100/100 证据评分
可用性 最后已知的活跃状态 最新存储的可达性观察
病毒检测总数:17/91 存储的阻止列表匹配项:2 品牌冒充:Google 最后已知的活跃状态
2026年4月8日 Google 1 Report Sent CDN

已存储的观测记录

观测到的标题差异

向扫描器显示的标题DezentraCore
向访客显示的标题SecureX AT

证据摘要

重要
Evidence score
100/100

securexat.cc is currently classified with an elevated risk level due to its active credential phishing threat. This domain attempts to steal user login information by impersonating legitimate services, putting users at significant risk of account compromise.

According to available intelligence, securexat.cc was created on April 08, 2026, and is registered through Gname.com Pte. Ltd. The domain resolves to IP address 104.21.14.134 and uses a Let's Encrypt SSL certificate to appear trustworthy. VirusTotal analysis flags 2 out of 95 security vendors, while Google Safe Browsing specifically identifies it for social engineering. These indicators collectively confirm the domain's malicious intent.

To mitigate the risk posed by securexat.cc, users should avoid clicking any links directing to this domain and never input credentials or personal information. Organizations should update email filters and blocklists to prevent delivery of messages containing this domain. Continuous monitoring for related phishing campaigns and user education on recognizing social engineering attempts are also recommended steps to reduce exposure.

已提交证据快照

已发送
台账记录
1
案件 ID
PD-20260408-1ADF20
已捕获页面标题
SecureX AT
PDF 文件
PDF 证据
完整证据文本
Registrar: Gname.com Pte. Ltd. (Singapore)
Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain
Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
VirusTotal
VirusTotal
17 det.
TLS 证书
Let's Encrypt
年龄
4 mo
观测状态
最后已知的活跃状态 HTTP 200
PhishDestroy
DestroyList
已列入
Reports Sent
1

Data Coverage

VirusTotal 17 / 91 URLQuery checked — no detections recorded PhishStats checked — no match recorded OTX no community references CF雷达 no data URLScan capture 存储的报告 URLScan verdict malicious DNS 阻断 12 已检查 — 未发现拦截 TLS valid certificate, 89d WHOIS 4 mo old 屏幕截图 2 captures · 2 sources 重定向链 未探查

威胁响应 Pipeline

发现
Checks
Reports
可用性
13/14

阻止列表覆盖

监控中的外部数据源 10 个 · 已存快照 2026年8月11日

监控中的外部数据源 8 个 无匹配

社区报告

由 1 名社区成员报告;首次发现于 2026年4月8日

已存储报告
1
已报告的唯一 URL
1
已接受1

社区情报

4 条社区报告

类别FAKE_PROJECT

Data submited by Intelligence for good

已保存的截图

域名情报

域名
URLScan Verdict 恶意 score 100 Phishing report ↗
Google Safe Browsing 已标记 Social engineering checked 2026年4月8日
服务器 / ASN cloudflare · AS13335 Cloudflare, Inc.
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
注册商 Gname SG(SG)
滥用举报联系方式complaint@gname.com
ICANN 注册管理机构ICANN官方认证注册商 →
IP 地址 104.21.14.134 CDN
地理位置CA Toronto, CA
网络AS13335 · Cloudflare, Inc.
源 IP 隐藏在 CDN 代理后面。边缘地址的反向 IP 结果包含不相关的租户;查找源头需要被动 DNS 或证书透明数据。
注册信息创建 2026年4月8日 (124d)
Elapsed Since First Report 19 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 最后已知的活跃状态.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
HTTP 状态码200
技术详情DNS、TLS 名称和时间戳
首次发现2026年4月8日
Submitted URLhttp://securexat.cc/
域名服务器cleo.ns.cloudflare.com
TLS 指纹
TLS 观测自 2026年4月8日 起有效扫描于 2026年4月9日
Favicon Hash
页面标题
SecureX AT
TLS 证书
Valid transport encryption · 颁发者 Let's Encrypt · valid for 89 days

取证情报

External Scripts 1
https://unpkg.com/vconsole@latest/dist/vconsole.min.js
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

17 / 91 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 13 detections
ADMINUSLabs
ChainPatrol
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
SOCRadar
Sophos
VIPRE
Webroot
网站性能分析

Google PageSpeed Insights — mobile performance audit of securexat.cc · checked Apr 8, 2026

45
Poor
Performance
FCP
9.83s
First Contentful Paint
LCP
10.3s
Largest Contentful Paint
CLS
0.072
Cumulative Layout Shift
TBT
412ms
Total Blocking Time
SI
9.83s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
网站配置分析
Stored observations are retained with their original collection time.
robots.txt Present · HTTP 200
Valid robots.txt; no Disallow/Allow paths were extracted.

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

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

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

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

97个国家目录
AI辅助草稿——事件详细信息由AI提供商处理 自行审核并提交

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

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

外部工具

ScamAdviserScamAdviser 信任评分 21/100状态: Likely Unsafe打开来源
HTML · IFRAME

嵌入此报告

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

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