robinhoodtism.com was observed with a Google Safe Browsing entry for social engineering on 2026-10-13. The domain also received a PageSpeed performance score of 63 on that date, capturing its technical response.
Recorded Evidence
VirusTotal recorded 14 detections from 92 scanners for robinhoodtism.com on 2026-10-03. Google Safe Browsing flagged the domain for social engineering on 2026-10-13. MetaMask and SEAL both listed the domain on their external blocklists as of 2026-10-13. PhishDestroy internally listed the domain on 2026-10-13. The domain was registered with Name.com, Inc. on 2026-07-10.
Interpretation
The VirusTotal record contains a quantitative measurement of detections from multiple scanners, documenting how robinhoodtism.com was assessed for security concerns. Google Safe Browsing provides a qualitative entry, naming social engineering as its recorded category. MetaMask and SEAL blocklist listings expand the scope of external checks, showing that several sources have documented entries for the domain. These records allow comparison of how different sources evaluated the domain on separate dates.
Recommended Actions
For robinhoodtism.com, preserve the VirusTotal detection record and Google Safe Browsing entry for future reference. Compare subsequent blocklist entries from MetaMask and SEAL with the current listings to monitor changes in external security documentation. Retain the PhishDestroy internal listing as an additional source for later analysis.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
캡처 라우팅
Local보관됨 2026-10-13 17:44:51 UTC
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
기술 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of robinhoodtism.com· checked Oct 13, 2026
63
Needs Work
Performance
FCP
4.1s
First Contentful Paint
LCP
4.1s
Largest Contentful Paint
CLS
0.265
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.1s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:http://robinhoodtism.com/
Final URL:https://www.robinhoodtism.com/
$TISM — The Only True Memestock Made by Robinhood
Robinhood hid a fake ticker on their own Legend page: $TISM, priced at $15. It's not fake anymore — it's tokenized and live on Robinhood Chain.
대응 HTTP 200
HTML body 231.8 KB
Compressed 167.6 KB
Links 10 internal · 6 external
Detected technologies
vue
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Open Graph title:$TISM — The Only True Memestock Made by Robinhood
Open Graph description:A fake ticker planted on robinhood.com/legend. Priced at $15 by Robinhood themselves. Not fake anymore — tokenized on Robinhood Chain.
Saved response-header values · 14
Access-Control-Allow-Origin
*
연령
0
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Tue, 13 Oct 2026 15:44:50 GMT
Etag
W/"d35578caa4cb8689c0e4e51286ad42e3"
Last-Modified
Tue, 13 Oct 2026 15:44:50 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000
Transfer-Encoding
chunked
X-Vercel-Cache
MISS
X-Vercel-Id
yul1::rvh2r-1791906290373-4b2c4ff2feac
Values retained by the collector; long values may be shortened during collection.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Status Check2026-10-13 15:50:43 UTC
Telemetry event observed.
Threat First Observed2026-10-13 15:49:50 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 216.150.16.65.
위협 대응 Pipeline
발견
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(SE)
