trezor.tips returned HTTP status 502 on 2026-10-01, according to the recorded HTTP check. The same domain was first observed on 2026-08-05, and a PhishDestroy internal listing is recorded as true.
Recorded Evidence
A VirusTotal check on 2026-09-12 recorded 20 detections across 89 scanners. OTX recorded 3 pulses on 2026-08-12, and the domain resolved to IP address 34.111.179.208 in the United States, associated with Google Cloud. The registrar is Name.com, Inc., and the SSL certificate was issued by Let's Encrypt / YE2, scanned on 2026-08-10. PageSpeed recorded a performance score of 56 on 2026-08-10.
Interpretation
The VirusTotal and OTX observations come from different dates, so their counts describe separate snapshots rather than one combined measurement. The HTTP check on 2026-10-01 and the first observation on 2026-08-05 also sit weeks apart, meaning the recorded status reflects only that check date. The PhishDestroy internal listing and the SSL scan add further dated context without establishing a current state.
Recommended Actions
Reviewers should retain the trezor.tips records with their exact dates and source labels so later checks can be compared against the same fields. Any new HTTP, VirusTotal, or OTX observation should be logged separately rather than merged with earlier values. During review, avoid submitting sensitive information to trezor.tips until the recorded signals have been independently verified.
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.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='trezor.tips', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 5, 2026
DOM Analysisanalyzed Sep 18, 2026score 98/10013 brand signals
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:31:48 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-24 22:14:41 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-24 22:14:41 UTC → 2026-09-30 16:14:55 UTC · 138.00hmidpoint estimate ≈ 2026-09-27 19:14:48 UTC · precision low · basis bounded
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.
Technologies · 8 identified
N
Node.js
Programming languages
Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside a web browser.
Express is a web application framework for Node.js, released as free and open-source software under the MIT License. It is designed for building web applications and APIs.
Last analyzed First positive detection Previous stored snapshot: 17 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
Lionic
Netcraft
PhishFort
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of trezor.tips· checked Aug 10, 2026
56
Needs Work
Performance
FCP
4.54s
First Contentful Paint
LCP
5.1s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
343ms
Total Blocking Time
SI
7.87s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Domain Status Transition2026-09-25 01:50:33 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-08-11 01:46:11 UTC
VirusTotal scanner detections updated from 17 to 17. Added scanner alerts: Gridinsoft. Resolved alerts: Seclookup.
Threat First Observed2026-08-10 05:23:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
15 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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
1209 hours elapsed from detection to the first unavailable 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 recordedContent unavailable
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 · trezor.tips
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.
Content matches4
Same favicon hash or the same page title as this host.
(SE)
