VirusTotal
16 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Prestige Luxerise | Official Website Platform”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
16 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
prestige-luxerise-app.com returned an HTTP 403 status during an HTTP check on 2026-10-01, a recorded denied response. The domain was first observed on 2026-09-15, and its registration date is 2026-02-17.
VirusTotal recorded 16 detections across 91 scanners on 2026-09-25. OTX listed 4 pulses on 2026-09-17, while the PhishDestroy internal listing flags the domain in that publisher catalogue. The registrar is NICENIC INTERNATIONAL GROUP CO., LIMITED, and the SSL certificate issuer is Let's Encrypt / YE2, scanned on 2026-09-16. PageSpeed recorded a performance score of 98 on 2026-09-15.
The VirusTotal and OTX entries are separate dated observations, each with its own scope and method. The HTTP 403 response and the PhishDestroy listing describe different recorded checks rather than a single condition. Because the dates differ, the records can be compared as points in time without treating them as one measurement.
Preserve the VirusTotal, OTX, and PhishDestroy records for prestige-luxerise-app.com for later comparison. Compare those source observations against future checks to see whether the recorded values change. Treat the recorded HTTP response as one reference point and review other source records before acting on the domain.
19 · datasets with records / 12 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
NICENIC INTERNATIONAL GROUP CO., LIMITED · 91.236.116.210 · DNS, TLS and retained responses
rocco.ns.cloudflare.comLocation describes the IP network.
0c44b6c0732216cfc3251e7221493951fd6715a33cb824f051f5929c4ea6ba22Saved 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 prestige-luxerise-app.com · checked Sep 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CaddyScanner note: alive_content: raw=short_403; http=403; via=https_proxy; server=Caddy
Collection history, report status and investigation channels
91.236.116.210.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
live_content→protected
http_access_restricted · access_restriction
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
live_content→Unknown
stale_current_evidence
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
protected→live_content
content_served
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
protected→Unknown
probe_inconclusive
Unknown→protected
http_access_restricted · access_restriction
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
17→16
Unknown
13 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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
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 ↗
prestige-luxerise-app.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
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
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “Prestige Luxerise | Official Website Platform”.
VirusTotal detections for prestige-luxerise-app.com: 16 (2026-09-25 02:07:23 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.