VirusTotal
10 / 89 engine detections
レポートを開く“GoHighLevel (GHL) CRM: Pricing, Features & 30-Day Trial”
MetaMaskなりすまし: ghlcrm.us — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 10/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
10 / 89 engine detections
レポートを開くDBL_PHISH
4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ghlcrm.us is a lookalike site that presents itself as GoHighLevel, the CRM and marketing-automation platform used by agencies and small businesses. Its page title, "GoHighLevel (GHL) CRM: Pricing, Features & 30-Day Trial", is written to catch people searching for GHL plans or a free trial. PhishDestroy first flagged it on 2026-09-11. As of 2026-10-19 the site was still online and serving content.
Impersonation pages like this copy a brand's pricing and signup flow so visitors believe they are on the official site. Anyone who clicks through to "start a trial" or "log in" can be asked for account credentials, business contact details or payment card information, and all of it goes to the operators instead of GoHighLevel. A stolen GHL login is especially valuable because these accounts usually hold client lists, connected email and SMS sending, and billing details for whole agencies.
When VirusTotal checked the domain on 2026-09-20, 10 of 89 engines flagged it. The vendors included alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. Spamhaus lists the domain in its DBL with a phishing designation. It also appears on the MetaMask and SEAL blocklists alongside PhishDestroy's. Four AlienVault OTX threat pulses reference it, which shows other researchers have tracked it independently.
The domain was registered through Namecheap on 2026-09-03, only eight days before PhishDestroy detected it. That short gap fits a site built for a quick campaign. It sits behind Cloudflare's network, geolocated to Canada, which hides the actual origin server. The Google Trust Services certificate gives the page a padlock in the browser, but that only means the connection is encrypted. It says nothing about who runs the site.
If you entered a GoHighLevel username and password on ghlcrm.us, change that password at once through the official GoHighLevel app. Turn on two-factor authentication, and review active sessions, API keys and connected integrations for anything you don't recognize. If you reused that password elsewhere, change it on those services too. If you submitted card details, call your bank to block the card and dispute any unfamiliar charges. Security teams should block the domain at DNS and proxy level. They should also search mail and web logs for staff who visited it, and warn anyone in marketing or sales who manages GHL accounts.
Last checked
Edge-IP の評判はこのドメインに起因しません。
skip.ns.cloudflare.comtina.ns.cloudflare.comroute3.mx.cloudflare.netpriority 18route1.mx.cloudflare.netpriority 21route2.mx.cloudflare.netpriority 65Location describes the IP network.
8118fa3a4a20e82c8a42982188ad3c2c06942cfa86b5447c689bb23710b99779Saved 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 ghlcrm.us · checked Sep 11, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
ghlcrm.us
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
4 community references
View sourceNo threat flag
View source10/89 engine detections
View sourceghlcrm.us
View sourcePage captured
View source保存された類似ドメイン:79 件
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 ↗
ghlcrm.us)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.