跳转到安全报告
域安全和威胁情报
adwords-google.ru favicon

adwords-google.ru

“Registered & Protected by MarkMonitor”

注册商
RU-CENTER-RU
Resolved IP
99.83.176.46
Registered
2012年2月16日
PhishDestroy assessment 高
可用性 最后已知的活跃状态 最新存储的可达性观察 观察到 · HTTP probe
存储的阻止列表匹配项:2 自动品牌标签:Google
OTX: 4 refs 2026年10月19日
API
该域名已被标记为恶意域名
报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
报告概览

冒充 Google: adwords-google.ru — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 0/92; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 66/100. 注册商…

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

Source evidenceVirusTotal 0 / 92 · OTX 4 references 5 sources

VirusTotal

0 / 92 engine detections

打开报告

Google Safe Browsing

No threat flag

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

高
VirusTotal
0 / 92
OTX
4 community refs
Page captures
2

PhishDestroy threat report

Overview

adwords-google.ru is a fake Google page designed to trick Google users into submitting their login credentials. PhishDestroy first recorded the site on 2026-10-19. The domain is still alive but its content was unreachable when last checked on 2026-10-19.

How the scam works

The page title reads “Registered & Protected by MarkMonitor,” a phrase often shown on legitimate Google‑related sites, to lend false credibility. Visitors are presented with a Google‑styled login form that captures usernames and passwords. Captured credentials can be used to hijack accounts or sold on underground markets.

Evidence

VirusTotal scanned the domain with 92 engines and reported zero detections, indicating the site evades many scanners. PhishDestroy, MetaMask and SEAL have all listed the domain, and OTX records four related threat pulses. No additional public blocklists or Google Safe Browsing warnings were found at the time of analysis.

Infrastructure

The domain was registered on 2012-02-16 through RU-CENTER-RU, giving the operators more than a decade of ownership before detection. Hosting is provided by Amazon.com, Inc. in the United States (IP 99.83.176.46, network AMAZON-02). The long registration period suggests a low‑cost, long‑term phishing infrastructure.

What to do

Anyone who entered Google credentials on this page should immediately change their password and enable two‑factor authentication, then review recent account activity for unauthorized access. If a Google account was linked to other services, revoke any suspicious app permissions. Defenders should block adwords-google.ru at the network perimeter, add it to internal phishing blocklists, and monitor for similar impersonation domains targeting Google.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 已列入 View source
PhishDestroy PhishDestroy list View source
SEAL 已列入 View source

Last checked

已保存的截图 · 2 captures

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
IP 信誉 abuse score 0/100 0 reports checked 2026年10月19日
OTX tags 2026-10activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 RU-CENTER-RU
注册信息创建 2012年2月16日 — Expires 2027年2月16日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年10月19日
DOM Analysisanalyzed 2026年10月19日score 0/100
Submitted URLhttp://adwords-google.ru/
Observed page title
Registered & Protected by MarkMonitor

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
99.83.176.46
Network ASN
AS16509
Organization
AMAZON-02 - Amazon.com, Inc., US
Observed location
US
Server header
awselb/2.0

域名服务器 2

  • ns1.markmonitor.com
  • ns3.markmonitor.com

Location describes the IP network.

Latest Classified Outcome 2026-10-19 22:49:39 UTC

Primary outcome 内容在线 reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation 内容在线 Ordinary HTTP content served 90% 2026-10-19 22:49:39 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-19 22:49:39 UTC last content: 2026-10-19 22:49:39 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
举报此域名 提交证据,帮助保护他人

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
Stored Capture Evidence 1 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: http://adwords-google.ru/
Registered & Protected by MarkMonitor
响应
HTTP 200
HTML body
1.6 KB
Compressed
867 B
Links
0 internal · 0 external
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-Protection
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 13
Accept-Ranges
bytes
Cache-Control
no-cache
Connection
keep-alive
Content-Length
1601
Content-Security-Policy
default-src 'self'; style-src 'unsafe-inline'; object-src 'none'
Content-Type
text/html; charset=UTF-8
Date
Mon, 19 Oct 2026 02:32:06 GMT
Etag
"641-64e91e28e3420"
Last-Modified
Fri, 03 Apr 2026 17:45:38 GMT
Pragma
no-cache
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→live_content

    content_served

  2. Availability monitor · First collection record

    可访问

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. VirusTotal

    0/92 engine detections

    View source
  4. Added to PhishDestroy

    adwords-google.ru

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

adwords-google.ru

证据与外部报告

深度分析
Help & reporting

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

3 evidence signal groups linked 0 stored notification records 最后已知的活跃状态

Listed domains receive at least one abuse report; this entry has no retained notification history.

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

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

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

我应该立即采取什么措施?

紧急

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • 更改所有密码 — 电子邮件、Exchange 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息?

联邦调查局(FBI)指南

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 adwords-google.ru)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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

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

实时威胁动态 对该列表提出异议
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

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

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