VirusTotal
13 / 91 engine detections
レポートを開く“Welcome to”
フィッシング: lrigma.shop — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 13/91 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 91 engine detections
レポートを開く悪意あり
レポートを開くDBL_PHISH
5 community references
レポートを開く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
lrigma.shop is an impersonation phishing page built to pass itself off as a legitimate service and harvest whatever visitors type into it. PhishDestroy first flagged it on 2026-09-24. As of 2026-10-19 the domain is still alive and now forwards visitors elsewhere through a redirect, so the threat has not gone away.
Impersonation sites copy the look, wording and flow of a familiar brand closely enough that a visitor follows the usual routine of signing in, verifying an account or completing a payment without second thoughts. Anything entered is captured by the operators, who can use it to take over the account, move funds or resell the data. This page carries only the generic, unfinished title "Welcome to" with no brand name, even though we classify it as impersonation. The active redirect means the same domain can steer victims to whichever lure the operators are running at the moment.
Thirteen of 91 VirusTotal engines flagged the domain on 2026-10-03, including alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Those engines come from separate vendors with their own detection pipelines, which makes a false positive unlikely. Spamhaus lists the domain in its DBL under the phishing category, which affects mail filtering and DNS-level blocking. It also appears in five AlienVault OTX threat pulses, so other researchers have tracked it as well.
The domain was registered on 2026-04-29 through GNAME.COM PTE. LTD., about five months before PhishDestroy detected it. That gap suggests it was registered in advance and left unused until the campaign started. The site sits behind Cloudflare London, LLC at 216.120.131.66, with the network located in the US, which hides the real origin server. Its Let's Encrypt certificate gives the page a browser padlock, but that only means the connection is encrypted and says nothing about whether the site is honest.
If you entered a password on lrigma.shop, change it right away on the real service and anywhere you reused it, then turn on two-factor authentication and sign out of other active sessions. If you entered card or bank details, contact your bank to block the card and dispute any unfamiliar charges. Watch for follow-up emails or texts that use the details you submitted. Defenders should block the domain at DNS, proxy and mail gateways and search logs for earlier visits or redirects through 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 の評判はこのドメインに起因しません。
a.share-dns.comb.share-dns.netLocation describes the IP network.
4cec5794fa835c2ea3f8fe82c5270ad4a2e07a7c0c13ce93a6d66f094e7036e5Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.lrigma.shopDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of lrigma.shop · checked Sep 24, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
到達可能
No threat flag
View source13/91 engine detections
View source5 community references
View sourcePage captured
View sourcelrigma.shop
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
lrigma.shop
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 ↗
lrigma.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.