VirusTotal
16 / 89 engine detections
レポートを開く“Attention Required! | Cloudflare”
フィッシング: ormexa.shop — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 16/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); Google Safe…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 89 engine detections
レポートを開く悪意あり
レポートを開くThreat flag recorded
レポートを開くDBL_PHISH
5 community references
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ormexa.shop is an impersonation phishing site that copied a legitimate service so visitors would trust it with their credentials or money. The brand it imitated is not identified, so treat any login form or payment request on this domain as hostile. PhishDestroy first flagged it on 2026-09-14. By 2026-09-15 it was offline, with its content blocked by the provider, and it remained dead when last checked on 2026-10-19.
Impersonation pages borrow a familiar brand's look and wording, then route the victim to a form that captures passwords, one-time codes, card details or wallet recovery phrases. Victims usually arrive through ads, search results or messages that make the fake site look official. Whatever they type goes straight to the operator, who can use it to take over accounts or drain funds. When last loaded, the page showed a Cloudflare "Attention Required!" challenge screen rather than a branded page, even though we classify the domain as impersonation phishing.
Sixteen of 89 VirusTotal engines flagged the domain on 2026-09-16. Those engines included Google Safe Browsing, BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, CRDF and alphaMountain.ai. Google Safe Browsing lists it under SOCIAL_ENGINEERING, and Spamhaus carries it in its DBL as a phishing domain. Five AlienVault OTX threat pulses reference it, so several separate researchers tracked this site, not one isolated report.
The domain was registered through Namecheap, Inc. on 2026-07-01, about 75 days before PhishDestroy detected it. The gap suggests it was registered in advance and held until a campaign was ready. Traffic went through Cloudflare's network on an address geolocated to Canada, which hides the real origin server. The certificate came from Google Trust Services, a free automated issuer, so the padlock in the browser said nothing about whether the site was legitimate.
If you entered a password on ormexa.shop, change it now, starting with the service the page imitated and any account that shares that password. Then turn on app-based two-factor authentication. If you entered card or bank details, call your card issuer to block the card and dispute any charges. If you typed a wallet recovery phrase, treat it as compromised and move your funds to a new wallet. Security teams should block the domain at DNS and proxy level, search logs for visits from 2026-07-01 onward, and reset credentials for any user who reached it.
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 の評判はこのドメインに起因しません。
amir.ns.cloudflare.comelisabeth.ns.cloudflare.comLocation describes the IP network.
14d68a959b79f1e6316ef9550ecd77aed9a71c682fa8de14e9ef14daf917002fSaved 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 ormexa.shop · checked Sep 14, 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
ormexa.shop
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
利用不可→到達可能
到達可能→利用不可
No flag recorded→Flag recorded
到達可能
5 community references
View sourceThreat flag recorded
View source16/89 engine detections
View sourcePage captured
View sourceormexa.shop
View sourceListed 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 ↗
ormexa.shop)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.