robinhoodtest.com was included in the MetaMask external blocklist on 2026-10-13, providing a dated indicator of its status in security monitoring. The domain also appeared in other technical intelligence sources, which expands the context of its recorded profile.
Recorded Evidence
VirusTotal checked robinhoodtest.com on 2026-10-11, documenting 15 detections out of 92 total scanners. OTX recorded three pulses for this domain as of 2026-10-13. The MetaMask and SEAL blocklists both listed the domain on 2026-10-13. PhishDestroy contains an internal listing for robinhoodtest.com. The domain was registered with Gname.com Pte. Ltd. on 2026-03-06, and its SSL certificate was issued by Let's Encrypt / YE2, scanned on 2026-10-13.
Interpretation
VirusTotal provides a technical measurement by recording detection counts from multiple scanners for robinhoodtest.com, reflecting how it was observed in automated security analysis. PhishDestroy’s internal listing represents a separate reference point, based on its own criteria. The evidence spans several sources, allowing for comparison of how robinhoodtest.com was documented across different intelligence and blocklist platforms.
Recommended Actions
For robinhoodtest.com, retain the VirusTotal detection records and OTX pulse counts for future reference and comparison. Preserve the MetaMask and SEAL blocklist entries to monitor any subsequent updates. Keep the PhishDestroy internal listing as part of the domain’s evidence archive for ongoing review.
Certificate hostname mismatch·
発行者 Let's Encrypt / YE2· stored validity ends in 31 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
154.82.111.63
Network ASN
AS399077
Organization
Tcloudnet
Observed location
Singapore, SG
Server header
nginx/1.27.0
ネームサーバー 4
a.share-dns.com
a5.share-dns.com
b.share-dns.net
b5.share-dns.net
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YE2
Valid from
2026-08-16 11:04:43
Valid until
2026-11-14 11:04:42
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-13 16:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfc25684f8dff670e7f747cfbed86028c68f6639d724916a9f288014050c6ce90Certificate names · 3 SANs
api.robinhoodtest.com
mana.robinhoodtest.com
www.robinhoodtest.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-13 15:51:48 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 15:51:48 UTC
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.
使用技術 · 3 identified
Google Sign-in
Authentication
Google Sign-In is a secure authentication system that reduces the burden of login for users, by enabling them to sign in with their Google account.
Google PageSpeed Insights — mobile performance audit of robinhoodtest.com· checked Oct 13, 2026
48
Poor
Performance
FCP
2.17s
First Contentful Paint
LCP
13.44s
Largest Contentful Paint
CLS
0.197
Cumulative Layout Shift
TBT
274ms
Total Blocking Time
SI
18.57s
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://robinhoodtest.com/
Final URL:https://robinhoodtest.com/
Robinhood
対応 HTTP 200
HTML body 901 B
Compressed 478 B
Links 0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.27.0
Content-Type: text/html
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Saved response-header values · 8
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
901
Content-Type
text/html
Date
Tue, 13 Oct 2026 15:52:25 GMT
Etag
"69f994c6-385"
Last-Modified
Tue, 05 May 2026 06:57:10 GMT
Server
nginx/1.27.0
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.
Threat First Observed2026-10-13 15:51:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 154.82.111.63.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
13 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.
(MY)
