The domain reach-trezor.io returned an HTTP status 200 on 2026-10-11, providing a dated technical record of a successful HTTP status observation. On the same date, the domain was listed on two external blocklists, which is a notable recorded indicator from multiple sources.
Recorded Evidence
On 2026-10-11, reach-trezor.io was included on the MetaMask and SEAL external blocklists. The HTTP status record for this domain on 2026-10-11 was 200. OTX documented reach-trezor.io in one pulse as of 2026-10-11. The domain was registered with OwnRegistrar, Inc. on 2026-10-04, and its SSL certificate was issued by Let's Encrypt / YE2.
Interpretation
The PhishDestroy internal listing contains a record of reach-trezor.io, documenting its presence in a security intelligence source. The HTTP status observation provides a technical measurement of the domain's web response on a specific date. The external blocklist entries and the OTX pulse reference show that reach-trezor.io was noted by several security sources, each using its own criteria for listing.
Recommended Actions
Preserve the MetaMask and SEAL blocklist records for reach-trezor.io as reference points for future comparison. Retain the OTX pulse and PhishDestroy internal listing records for this domain to support ongoing review. Keep the HTTP status 200 record as a technical benchmark for past network response.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 09:55:41 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-11 09:55:41 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.
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-11 09:55:41 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
reach-trezor.io detected and queued for full analysis
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
4 evidence signal groups linked0 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · reach-trezor.io
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
