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

facebook-login-facebook[.]blogspot[.]com

“facebook”

威胁判定 关键 100/100 证据评分
可用性 最后已知的活跃状态 最新存储的可达性观察
病毒检测总数:18/91 品牌冒充:Facebook 最后已知的活跃状态
2026年2月19日 Facebook
报告概览

facebook-login-facebook.blogspot.com — 最后已知的活跃状态 (HTTP 200). 品牌冒充:Facebook; 诈骗类型:Social Media Phishing. 证据摘要: VirusTotal 18/91 (ADMINUSLabs, Criminal IP, alphaMountain.ai, BitDefender, Chong Lua Dao); PhishDestroy score 100/100. 注册商: MarkMonitor.

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

证据摘要
重要
Ref
E9FB1317
评分
100/100

This domain, facebook-login-facebook.blogspot.com, is identified as a brand impersonation threat targeting Facebook users. Analysis indicates the page mimics Facebook's login interface, as evidenced by the page title 'facebook,' with the objective of harvesting user credentials. No crypto drainer kit signatures were observed, but the domain's structure and content align with credential phishing tactics commonly deployed against social media platforms. Infrastructure analysis reveals the domain was registered through MarkMonitor, Inc., a registrar frequently associated with legitimate enterprises but occasionally exploited for phishing. The domain resolves to IP address 142.251.141.97, hosted under AS15169 (Google LLC) in the United States. It was created on February 21, 2026, though this date may reflect backdating or registrar data anomalies. Detection metrics show 20 out of 95 security vendors flagged the domain on VirusTotal, while it appears on one security blocklist and is actively blocked by at least one anti-phishing system. The SSL certificate, issued by Google Trust Services (WE2), does not mitigate the domain's malicious intent. As of the latest assessment, facebook-login-facebook.blogspot.com has been taken offline, likely following abuse reports or automated takedown mechanisms. However, the elevated risk persists due to the domain's prior activity and the potential for re-registration or migration to alternative hosting. Users are advised to verify domain authenticity before entering credentials, particularly on platforms hosted under non-corporate subdomains. Organizations should monitor for similar impersonation attempts leveraging blogspot.com or other free hosting services, as these remain prevalent vectors for credential theft campaigns.

VirusTotal
VirusTotal
18 det.
DNS Security
6/14
URLScan
URLScan
TLS 证书
WE2
Hosting
Blogger (Google)
观测状态
最后已知的活跃状态 200
PhishDestroy
DestroyList
已列入
数据覆盖范围 VirusTotal 18 / 91 URLQuery 报告已存储 — 详细判决待定 PhishStats checked — no match recorded OTX no community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict 分析完成 DNS 阻断 6/14 TLS valid certificate, 58d WHOIS not parsed 屏幕截图 2 captures · 2 sources 重定向链 未探查
网络安全情报
DNS Provider Blocks 6 / 14
Brand Facebook Cloudflare Family Cloudflare Security Controld Adblock Controld Family Controld Malware
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
可用性
16/18

公共封禁名单状态

已保存的截图

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN GSE · AS15169 Google LLC
IP 信誉 abuse score 0/100 0 reports checked 2026年8月14日
平台提供商 MarkMonitor US(US)
滥用举报联系方式network-abuse@google.com
IP 地址 142.251.141.97 US
地理位置US Mountain View, US
网络AS15169 · Google LLC
Elapsed Since First Report 24 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 最后已知的活跃状态.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
HTTP 状态码200
技术细节DNS、SSL SAN、时间戳
首次发现2026年2月19日
DOM Analysisanalyzed 2026年7月10日score 93/100
IoC Extractionscanned 2026年7月29日0 wallet · 0 Telegram IoCs
Submitted URLhttp://facebook-login-facebook.blogspot.com/
TLS Observationvalid from 2026年2月2日scanned 2026年3月15日
页面标题
facebook
TLS 证书
Valid transport encryption · 颁发者 WE2 · valid for 58 days
所用技术 · 6 identified
Blogger
Java
Python
O
OpenGSE
Google AdSense

Advertising platform — conversion and remarketing tracking pixel.

HTTP/3
Miscellaneous

Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.

Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

18 / 91 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 20 detections
ADMINUSLabs
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Netcraft
OpenPhish
Sophos
VIPRE
Webroot

存档证据

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

Google PageSpeed Insights — mobile performance audit of facebook-login-facebook.blogspot.com · checked Mar 1, 2026

93
Good
Performance
FCP
2s
First Contentful Paint
LCP
2.91s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.82s
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
/search /share-widget
Sitemap 0 pages · HTTP 200

证据与外部报告

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

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/facebook-login-facebook.blogspot.com"
  title="PhishDestroy threat report for facebook-login-facebook.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>