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

coinbaseloggin[.]blogspot[.]com

“Blog not found”

威胁判定 关键 100/100 证据评分
可用性 内容不可用 最新观察中的内容不可用
病毒检测总数:17/91 存储的阻止列表匹配项:2 URLQuery threat systems: 1 alert 品牌冒充:Coinbase
2026年5月25日 Coinbase

证据摘要

重要
Evidence score
100/100

This domain, coinbaseloggin.blogspot.com, is a confirmed brand impersonation site designed to deceive users by mimicking the legitimate Coinbase cryptocurrency exchange platform. The site likely aims to harvest login credentials, enabling attackers to gain unauthorized access to victims' accounts, exfiltrate sensitive personal data, or initiate unauthorized transactions. Given the high-risk nature of cryptocurrency-related fraud, users who interact with this domain may face immediate financial loss or long-term account compromise. The impersonation tactic leverages the trust associated with the Coinbase brand to lower user vigilance and increase the likelihood of successful credential theft. Analysis of the domain reveals multiple technical indicators supporting its malicious classification. The domain is flagged by 17 out of 95 security vendors on VirusTotal, indicating a broad consensus on its harmful nature. It is registered through Google Blogger, a platform frequently abused for hosting impersonation pages due to its ease of setup and lack of stringent verification. The domain appears on three independent security blocklists, further corroborating its malicious intent. Infrastructure analysis shows it resolves to the IP address 142.251.20.132, which is associated with legitimate Google services but has been co-opted for hosting this fraudulent content. The page currently displays a 'Blog not found' message, suggesting it may have been taken down or is in a dormant state, though residual risk remains for users who previously interacted with it. Users who visited coinbaseloggin.blogspot.com should take immediate remedial actions to mitigate potential compromise. First, any credentials entered on the site must be considered exposed and should be reset immediately across all platforms where the same or similar passwords were used. Multi-factor authentication (MFA) should be enabled on all critical accounts, particularly those related to cryptocurrency or financial services. Users are advised to review their Coinbase account activity for unauthorized transactions or changes to security settings. If any suspicious activity is detected, the account should be locked, and the platform's official support channels should be contacted for further investigation. Additionally, monitoring for phishing attempts via email or other vectors is recommended, as attackers may attempt follow-up exploitation using harvested credentials.

VirusTotal
VirusTotal
17 det.
URLQuery
URLQuery
1 threat alert
DNS Security
3/14
CF雷达
恶意
TLS 证书
Google Trust Services
Hosting
Blogger (Google)
年龄
3 mo New
观测状态
内容不可用 HTTP 404
PhishDestroy
DestroyList
已列入

Data Coverage

VirusTotal 17 / 91 URLQuery 1 threat-system alert PhishStats checked — no match recorded OTX no community references CF雷达 provider verdict: malicious URLScan capture 存储的报告 URLScan verdict 无可用判定 DNS 阻断 3/14 TLS valid certificate, 65d WHOIS 3 mo old 屏幕截图 2 captures · 2 sources 重定向链 未探查
网络安全情报
DNS Provider Blocks 3 / 14
Brand Base Brand Coinbase Quad9 Secure
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU coinbaseloggin.blogspot.com malicious Sinkholed
CF Cloudflare Radar Verdict 恶意
Phishing
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月12日

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

已保存的截图

域名情报

域名
服务器 / ASN AS15169 Google LLC
IP 信誉 IP abuse confidence 0/100 24 reports checked 2026年7月13日
平台提供商 Google Blogger US(US)
滥用举报联系方式network-abuse@google.com
IP 地址 142.251.20.132 US
地理位置US Mountain View, US
网络AS15169 · Google LLC
HTTP 状态码404 Not Found
首次不可用所需时间 16h
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情DNS、TLS 名称和时间戳
首次发现2026年5月25日
Submitted URLhttp://coinbaseloggin.blogspot.com/
TLS 观测自 2026年5月7日 起有效
页面标题
Blog not found
TLS 证书
Valid transport encryption · 颁发者 Google Trust Services · valid for 65 days

技术

识别出 5 项高置信度技术

Blogger Java Python OpenGSE HTTP/3
Cloudflare Radar
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

17 / 91 安全供应商标记了该域
View on VT
Last analyzed
ADMINUSLabs
ChainPatrol
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Emsisoft
Fortinet
G-Data
卡巴斯基
LevelBlue
Lionic
Netcraft
Sophos
VIPRE
Webroot
网站性能分析

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

86
Needs Work
Performance
FCP
2.98s
First Contentful Paint
LCP
3.28s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
132ms
Total Blocking Time
SI
2.98s
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/coinbaseloggin.blogspot.com"
  title="PhishDestroy threat report for coinbaseloggin.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>