VirusTotal
6 / 89
“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.
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
ApacheScanner note: redirect: raw=redirect_301; http=301; via=https_direct; location=https://www.luckysamudra.com/; server=Apache
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
103.119.228.121. 10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
PD-20260911-6F6BF9 Recipient: abuse@mvnet.co.id Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (ID): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and ID's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive