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

robux-skrip[.]blogspot[.]com

“Free Robux”

威胁判定 关键 76/100 证据评分
可用性 最后已知的活跃状态 最新存储的可达性观察
风险信号
病毒检测总数：1/91 品牌冒充：Google 最后已知的活跃状态
2026年7月31日 Google

证据摘要

重要
Evidence score
76/100

As of July 31, 2026, the domain robux-skrip.blogspot.com is flagged for potential phishing activity. This domain appears on one security blocklist, specifically PhishDestroy, which indicates a known risk associated with the site. The domain is registered through Google LLC, a common registrar for Blogger sites, which can sometimes be used for temporary or low-cost phishing operations. The nameservers for this domain are not found, which might suggest an unusual or non-standard DNS configuration, or it could be a transient issue.

The domain resolves to the IP address 142.251.14.132, which is part of Google's infrastructure. This IP resolution to Google's network is not definitive proof of the domain's legitimacy, as it is possible for phishing sites to use Google's hosting services, particularly Blogger, to appear more credible. The current status of the domain is active, and it remains accessible, suggesting ongoing activity.

The exact content of the site has not yet been analyzed, and no specific page title or brand target is known from the provided intelligence. Defenders should exercise caution and consider blocking access to this domain until further analysis confirms its safety. Given the domain's presence on a security blocklist and its active status, it is advisable for network administrators to monitor traffic to this site and implement additional security measures to protect users from potential phishing attacks.

VirusTotal
VirusTotal
1 det.
TLS 证书
Google Trust Services
观测状态
最后已知的活跃状态 HTTP 200
PhishDestroy
DestroyList
已列入

Data Coverage

VirusTotal 1 / 91 URLQuery 未检查 PhishStats 未检查 OTX no community references CF雷达 no data URLScan capture 存储的报告 URLScan verdict 分析完成 DNS 阻断 未检查 TLS valid certificate, 51d WHOIS not parsed 屏幕截图 2 captures · 2 sources 重定向链 未探查

威胁响应 Pipeline

发现
Checks
Reports
可用性
13/15

阻止列表覆盖

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

PhishDestroy 源数据集
监控中的外部数据源 10 个 无匹配
MetaMask 无匹配 ScamSniffer 无匹配 Polkadot 无匹配 CryptoFirewall 无匹配 OpenPhish 无匹配 SEAL 无匹配 Enkrypt 无匹配 Phishunt 无匹配 Codeesura 无匹配 DiscordPhishing 无匹配

检测时间线

  1. 首次记录

    首次存储值：可访问

  2. VirusTotal

    None → 0

已保存的截图

URLScan capture 2 / 2
查看原图 Wayback 下载

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN GSE · AS15169 GOOGLE - Google LLC, US
IP 信誉 IP abuse confidence 0/100 35 reports checked 2026年7月31日
平台提供商 Google Domains US(US)
滥用举报联系方式network-abuse@google.com, abuse@google.com
IP 地址 142.251.14.132 DE
地理位置DE Frankfurt am Main, DE
网络AS15169 · Google LLC
反向 IPviewdns.info → rapiddns.io →
HTTP 状态码200
技术详情DNS、TLS 名称和时间戳
首次发现2026年7月31日
DOM Analysisanalyzed 2026年7月31日DOM analysis score 76/1003 brand signals
Submitted URLhttps://robux-skrip.blogspot.com/?… query redacted
TLS 指纹
TLS 观测自 2026年6月29日 起有效扫描于 2026年7月31日
TLS 主体备用名称blogspot.aeblogspot.alblogspot.amblogspot.bablogspot.beblogspot.bgblogspot.cablogspot.chblogspot.clblogspot.co.atblogspot.co.idblogspot.co.ilblogspot.co.keblogspot.co.nzblogspot.co.uk+55
页面标题
Free Robux
Impersonates
Google Roblox Robux
TLS 证书
Valid transport encryption · 颁发者 Google Trust Services · valid for 51 days
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

1 / 91 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
Forcepoint ThreatSeeker

存档证据

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

Google PageSpeed Insights — mobile performance audit of robux-skrip.blogspot.com · checked Jul 31, 2026

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

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://robux-skrip.blogspot.com/
Free Robux
响应
HTTP 200
HTML body
18.7 KB
Compressed
6.8 KB
Links
1 internal · 0 external
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0
Content-Encoding: gzip
Server: GSE
Security headers present
X-Content-Type-OptionsX-XSS-Protection
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
All stored response-header names (12)
Content-TypeExpiresDateCache-ControlLast-ModifiedEtagContent-EncodingX-Content-Type-OptionsX-XSS-ProtectionServerAlt-SvcTransfer-Encoding
Archived
网站配置分析
Stored observations are retained with their original collection time.
robots.txt Present · HTTP 200
/search /share-widget
Observed 2026-07-31 14:05:21 UTC · scan archive
Sitemap 0 pages · HTTP 200
Observed 2026-07-31 14:05:21 UTC · scan archive

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

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

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

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

向当地主管部门报告

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

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

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

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

外部工具

ChainPatrol URLQuery Google Safe Browsing SSL Labs Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
HTML · IFRAME

嵌入此报告

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

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