VirusTotal
6 / 89 engine detections
보고서 열기“Lucky Samudra”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@mvnet.co.id.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
luckysamudra.com — 마지막으로 알려진 활성 (HTTP 301). 사기 유형: Impersonation. 증거 요약: VirusTotal 6/89 (alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Gridinsoft, Seclookup); URLQuery 2 alerts; PhishDestroy score 88/100. 등록기관: Key-Systems.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
6 / 89 engine detections
보고서 열기2 threat-system alerts
보고서 열기5 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.
AI-assisted evidence review
The domain luckysamudra.com returned an HTTP 301 status when checked on 2026-10-01, according to the recorded HTTP observation. The same evidence set notes that the domain was first observed on 2026-09-11, giving a separate date for the earliest sighting in this record.
The HTTP check on 2026-10-01 recorded status 301 for luckysamudra.com. A PhishDestroy internal listing was recorded, and OTX was checked on 2026-09-11 with one pulse noted. VirusTotal recorded 6 detections across 89 scanners on 2026-09-21. The registration date is 2002-03-04 with Key-Systems GmbH as registrar, and the SSL scan on 2026-09-11 named Let's Encrypt / YR1 as issuer.
The OTX check and the VirusTotal check carry different dates, so their observations describe separate points in time rather than one combined snapshot. The PhishDestroy internal listing and the HTTP status also come from different checks, which means a reader should compare them as distinct dated records. Because the observation dates differ, later checks may show different results from those recorded here.
Anyone reviewing luckysamudra.com should retain the dated records, including the 2026-10-01 HTTP observation and the 2026-09-21 VirusTotal result, so later comparisons rest on the same source values. Subsequent checks of luckysamudra.com should be logged with their own dates before any conclusion is drawn from earlier entries. During review, avoid submitting sensitive information to the domain until the recorded status and listing are independently confirmed.
dns1.techscape10.comdns2.techscape10.comluckysamudra.compriority 0Location describes the IP network.
223faad57c47eb5c4dfd60178402c193e01634e5e2bf0d28a8fa882ccd3b6e3bSaved 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 luckysamudra.com · 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.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://www.luckysamudra.com/; server=Apache
luckysamudra.com
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
접속 가능
5 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePD-20260911-6F6BF9
Page captured
View sourceluckysamudra.com
View sourcePD-20260911-6F6BF9 Recipient: abuse@mvnet.co.id 계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
luckysamudra.com)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.