VirusTotal
11 / 91 engine detections
レポートを開く“Google”
Gmailなりすまし: genesis-monad.events — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/91 (ChainPatrol, alphaMountain.ai, BitDefender, CyRadar, Fortinet); Google…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 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
Analysis of genesis-monad.events, observed on July 24, 2026, indicates a high‑risk brand‑impersonation campaign targeting Gmail users. The domain resolves to IP 142.250.181.228, which belongs to AS15169 Google LLC and is geolocated in the United States. DNS resolution is served by Cloudflare with the authoritative nameservers brenna.ns.cloudflare.com and hassan.ns.cloudflare.com, and the domain was registered through Cloudflare, Inc. The TLS certificate presented is issued by Google Trust Services under the WE1 designation, which is typical for legitimate Google services but does not guarantee authenticity of the hosting site. An HTTP request returns a 403 status code, and the page title reported by passive measurements is “Google,” matching the targeted brand.
Reputation checks show that the domain is listed on one security blocklist and is flagged by Google Safe Browsing for social‑engineering content. VirusTotal analysis records 11 of 95 security vendors marking the domain as malicious, and the site is actively blocked by the PhishDestroy filtering service. Gridinsoft assigns a trust score of 0 out of 100, reinforcing the malicious assessment. The only technology identified is Cloudflare, which is commonly used by both legitimate and illicit operators.
The evidence points to a deliberate attempt to lure Gmail users by mimicking Google branding, yet the site is currently offline, limiting real‑time observation. Defenders should continue to block the domain at perimeter and DNS layers, monitor for any re‑registration attempts, and add the IP address to threat‑intel feeds. Additional scrutiny of related subdomains and any future TLS certificates issued for this FQDN is recommended, as well as periodic re‑scanning to capture potential changes in hosting or content.
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.
803261b2bb1e86716556294c1e6c07a9430a970540df21c19e4d0f50d5e1aff9Saved 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 genesis-monad.events · checked Apr 12, 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
genesis-monad.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/7dc3a56d-9dbf-4736-82fd-1eb068d1bb73
到達可能→利用不可
11/91 engine detections
View sourcePage captured
View sourceThreat flag recorded
View sourcegenesis-monad.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 ↗
genesis-monad.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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.