跳转到安全报告
⚠️
该域名已被标记为恶意域名
安全引擎报告检测:2。 报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
域安全和威胁情报

coinbasezsupport[.]blogspot[.]com

“coinbase support phone number Ⓡ +1 (888) 897-5990 || Contact coinbase support”

威胁判定 关键 71/100 证据评分
可用性 内容不可用 最新观察中的内容不可用
病毒检测总数:2/94 存储的阻止列表匹配项:2 品牌冒充:Coinbase
2026年3月26日 Coinbase

已存储的观测记录

观测到的标题差异

向扫描器显示的标题Blog not found
向访客显示的标题coinbase support phone number Ⓡ +1 (888) 897-5990 || Contact coinbase support
证据摘要
重要
评分
71/100

PhishDestroy identifies a live brand impersonation scam hosted at coinbasezsupport.blogspot.com, where attackers masquerade as Coinbase support to harvest user credentials and financial data. This domain leverages a deceptive blogspot subdomain to exploit trust in the legitimate Coinbase brand, aiming to mislead victims into disclosing sensitive account information or payment details. The threat actor behind this domain employs social engineering tactics, posing as official support staff to manipulate users into performing actions that compromise their security. Given the domain’s active status and the absence of detections on VirusTotal, it represents a significant risk to unsuspecting crypto users seeking legitimate assistance. Technical analysis of coinbasezsupport.blogspot.com reveals a sophisticated impersonation campaign, with the domain resolving to IP 142.251.127.132 and operating under an SSL certificate issued by Google Trust Services, which may lend an air of legitimacy to the fraudulent site. As of the latest scan, the domain remains undetected by 95 security vendors on VirusTotal, indicating a low initial detection rate that could allow the threat to persist undetected. While the exact creation date is not publicly available, the lack of blocklist entries further underscores the stealthy nature of this campaign. The use of a blogspot subdomain—a platform typically associated with benign content—adds a layer of obfuscation, making it easier for the domain to evade traditional security measures and blend into legitimate traffic. Users who have visited coinbasezsupport.blogspot.com should immediately assess whether they entered any credentials or financial information on the site. If sensitive data was disclosed, reset passwords for Coinbase and any other accounts where the same credentials were reused, and enable multi-factor authentication where available. Additionally, scan devices for malware or unauthorized access, as the threat actor may attempt to maintain persistence on compromised systems. Report the domain to Coinbase’s official support channels and consider blocking it at the network level to prevent further exposure. Vigilance is critical in mitigating the risks posed by this impersonation scam, and users are advised to verify the authenticity of support channels directly through Coinbase’s official website or verified social media accounts.

VirusTotal
VirusTotal
2 det.
DNS Security
2/12
TLS 证书
Google Trust Services
Hosting
Blogger (Google)
年龄
5 mo
观测状态
内容不可用 404
PhishDestroy
DestroyList
已列入
数据覆盖范围 VirusTotal 2 / 94 URLQuery checked — no detections recorded PhishStats checked — no match recorded OTX no community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict malicious DNS 阻断 2/12 TLS valid certificate, 66d WHOIS 5 mo old 屏幕截图 3 captures · 3 sources 重定向链 未探查
网络安全情报
DNS Provider Blocks 2 / 12
Brand Base Brand Coinbase
Free Hosting Detected Blogger (Google)
This domain is hosted on Blogger (Google) (free blog platform). Free hosting platforms are commonly used for both legitimate testing/development and malicious purposes. Additional context is needed fo

威胁响应 Pipeline

发现
Checks
Reports
可用性
15/16

阻止列表覆盖

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

检测时间线

  1. VirusTotal

    None → 0

已保存的截图

域名情报

域名
URLScan Verdict 恶意 score 100 Phishing brand: Coinbase report ↗
服务器 / ASN GSE · AS15169 Google LLC
IP 信誉 abuse score 0/100 18 reports checked 2026年7月14日
平台提供商 Google Blogger US(US)
滥用举报联系方式network-abuse@google.com
IP 地址 142.251.127.132 US
地理位置US Mountain View, US
网络AS15169 · Google LLC
HTTP 状态码404 Not Found
首次不可用所需时间 17h
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情DNS、TLS 名称和时间戳
首次发现2026年3月26日
Submitted URLhttp://coinbasezsupport.blogspot.com/
TLS 指纹
TLS 观测自 2026年3月9日 起有效扫描于 2026年3月27日
TLS 主体备用名称blogspot.aeblogspot.alblogspot.amblogspot.bablogspot.beblogspot.bgblogspot.cablogspot.chblogspot.clblogspot.co.atblogspot.co.idblogspot.co.ilblogspot.co.keblogspot.co.nzblogspot.co.uk+55
页面标题
coinbase support phone number Ⓡ +1 (888) 897-5990 || Contact coinbase support
TLS 证书
Valid transport encryption · 颁发者 Google Trust Services · valid for 66 days
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

2 / 94 安全供应商标记了该域
View on VT
Last analyzed
卡巴斯基
LevelBlue
网站性能分析

Google PageSpeed Insights — mobile performance audit of coinbasezsupport.blogspot.com · checked Mar 26, 2026

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

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

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

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

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

向当地主管部门报告

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

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

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

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

外部工具

HTML · IFRAME

嵌入此报告

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

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