VirusTotal
12 / 91 engine detections
打开报告“Google”
冒充 Google: gmonad.events — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 12/91 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar); Google Safe…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
12 / 91 engine detections
打开报告Threat flag recorded
打开报告no community references
打开报告provider verdict: clean
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, gmonad.events, is actively engaged in brand impersonation targeting Google, a high-risk threat designed to deceive users into disclosing sensitive credentials or installing malicious payloads. The page title mimics legitimate Google services, displaying "Google" to enhance credibility and trick victims into interacting with fraudulent content. Analysis indicates the domain is structured to replicate authentic Google login portals, increasing the likelihood of successful phishing attempts against unsuspecting users. Infrastructure analysis reveals the domain resolves to 142.250.185.132, an IP address geolocated within the United States under AS15169 (Google LLC), though it is registered through Cloudflare, Inc. Security vendors on VirusTotal have flagged gmonad.events as malicious, with 14 out of 95 engines detecting phishing or fraudulent activity. The domain appears on one security blocklist and is currently classified as active. Its SSL certificate, issued by Google Trust Services (WE1), further complicates detection by presenting a seemingly legitimate encrypted connection. Users who have visited gmonad.events should immediately revoke any credentials entered on the site and monitor associated accounts for unauthorized activity. System administrators are advised to block the domain and its resolving IP (142.250.185.132) at the network perimeter. If browser-based interaction occurred, clear cached data and run a full antivirus scan to detect potential secondary infections. Organizations should review logs for connections to the domain or IP to assess compromise scope.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP 声誉不属于此域。
brenna.ns.cloudflare.comhassan.ns.cloudflare.comLocation describes the IP network.
d99331828726027b9ba4facbb7a6472a484345a937fda2178a0b53de59a95356Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of gmonad.events · checked Apr 13, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
gmonad.events
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不可用→可访问
可访问→不可用
不可用→可访问
不可用→可访问
https://radar.cloudflare.com/scan/0bb9ee8d-c3ad-40ae-85f4-25f7ef6e159f
可访问→不可用
12/91 engine detections
View sourcePage captured
View sourceThreat flag recorded
View sourcegmonad.events
View source由 1 名社区成员报告;首次发现于 2025年11月25日
Listed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
gmonad.events)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.