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.
DOM Analysisanalyzed 2026年4月11日score 88/1001 brand signal
Submitted URLhttp://gmonad.events/
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
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.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
