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

cybermedic.buzz

“404 Not Found”

威胁判定 关键 83/100 证据评分
可用性 内容不可用 最新观察中的内容不可用
风险信号
病毒检测总数：10/89 品牌冒充：Unknown
OTX: 3 refs 2026年9月4日 未知
Actions API
⚠️
该域名已被标记为恶意域名
安全引擎报告检测：10。 请格外小心——不要输入凭据或个人信息。
报告概览

cybermedic.buzz — 内容不可用 (HTTP 404). 品牌冒充：Unknown; 诈骗类型：Impersonation. 证据摘要: VirusTotal 10/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data); PhishDestroy score 83/100. 注册商: Spaceship.

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

证据摘要

重要
评分
83/100

PhishDestroy first observed cybermedic.buzz on Sep 4, 2026. Stored content metadata identifies Unknown as the apparent target. The captured page title is “404 Not Found”. Stored page analysis classifies the content as impersonation. Campaign clustering links the hostname to the Unknown kit. Current evidence score: 83/100 (critical).

One source contains a positive finding: VirusTotal. VirusTotal recorded 10 detections among 89 engines: alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Kaspersky, SOCRadar, Sophos, VIPRE on Sep 12, 2026 at 02:19 UTC. Non-positive and contextual checks: AlienVault OTX listed 3 community pulse references (not vendor detections) on Sep 10, 2026 at 23:51 UTC. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 22:20 UTC. Google Safe Browsing returned no flag on Sep 16, 2026 at 04:00 UTC. URLScan completed without a malicious verdict (score 0) on Sep 4, 2026 at 23:08 UTC.

HTTP 404 was recorded on Sep 19, 2026 at 01:17 UTC; content was unavailable. Registration records for the domain list Spaceship, Inc. as the registrar and Jul 21, 2026 as the creation date. At collection time, the hostname resolved to 34.75.127.116 on AS396982 (Google LLC). The recorded endpoint location is North Charleston, US. The stored server header is nginx. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt as the certificate issuer.

Stored content provides classification context, but only one source contains a positive finding.

VirusTotal
VirusTotal
10 det.
OTX references
3 community refs
URLScan
URLScan
报告 ↗
TLS 证书
Let's Encrypt
年龄
2 mo New
观测状态
内容不可用 404
PhishDestroy
DestroyList
已列入
数据覆盖范围 VirusTotal 10 / 89 OTX 3 community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict 分析完成 TLS valid certificate, 43d WHOIS 2 mo old 屏幕截图 2 captures · 2 sources

Forensic History & Detection Timeline

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. VirusTotal Detections Update Sep 11, 2026 · 01:50 UTC
    VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: VIPRE.
  2. VirusTotal Detections Update Sep 6, 2026 · 00:53 UTC
    VirusTotal scanner detections updated from 1 to 4. Added scanner alerts: CRDF, Gridinsoft, SOCRadar.
  3. Domain Status Transition Sep 5, 2026 · 00:15 UTC
    Domain state transitioned from dead to alive.
  4. Domain Status Transition Sep 5, 2026 · 00:00 UTC
    Domain state transitioned from alive to dead.
  5. Threat First Observed Sep 4, 2026 · 19:20 UTC
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.75.127.116.

威胁响应 Pipeline

发现
Checks
Reports
可用性
17/18

公共封禁名单状态

Evasion analysis

Cloaking & traffic-distribution check

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
nginx

Scanner note: dead_http: raw=http_404; http=404; via=https_proxy; server=nginx

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this section scrolls into view.
Waiting

已保存的截图 · 2 sources

Primary capture 1 / 2
来源Primary capture
Captured2026-09-04 15:57 UTC
StateStored capture
Position1 / 2
查看原图 Open raw image Wayback 下载
页面标题
404 Not Found
TLS 证书
Valid transport encryption · 颁发者 Let's Encrypt · valid for 43 days

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN nginx · AS396982 Google LLC
IP 信誉 abuse score 0/100 0 reports checked 2026年9月4日
OTX Tags 2026-09activeall-domainsblocklistcontentcrypto域名drainerfraudmonthlyphishdestroyphishingscam
注册商 Spaceship US(US)
ICANN 注册管理机构ICANN官方认证注册商 →
WHOIS查询cybermedic.buzz 的 ICANN RDAP →
IP 地址 34.75.127.116 US
地理位置US North Charleston, US
网络AS396982 · Google Cloud (us-east1)
反向 IPviewdns.info → rapiddns.io →
注册信息创建 2026年7月22日 (60d · New)
HTTP 状态码404 Not Found
首次不可用所需时间 6h
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情DNS、SSL SAN、时间戳
首次发现2026年9月4日
IoC Extractionscanned 2026年9月10日0 wallet · 0 Telegram IoCs
Submitted URLhttp://cybermedic.buzz/
域名服务器launch2.spaceship.net
Favicon Hash
SHORTDOT 域名区 · 公开证据 .buzz

ShortDot zone evidence

The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.

ShortDot SA · Luxembourg 7 个域名区 · 全区证据每日更新 打开 ShortDot 证据库
ICANN OVERSIGHT

认证和 RAA 背景

Registrar accreditation and DNS abuse obligations

For this gTLD, 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 不会自动发送任何内容。
技术 · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

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

Google PageSpeed Insights — mobile performance audit of cybermedic.buzz · checked Sep 4, 2026

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

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 10 det. ChainPatrol URLQuery Open lookup SSL 实验室 Stored TLS valid CF雷达 Open report OTX 3 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
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接 深度分析

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

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

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

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

向当地主管部门报告

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

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

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

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

嵌入此报告

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

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