VirusTotal
14 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
No page capture has been retained for this domain.
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.
14 / 89
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_ABUSED_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
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.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, an HTTP check of trerjhrdwallet.gitbook.io returned status 307, a redirect response recorded on that date. The same domain appears in the publisher-owned PhishDestroy catalogue, which is the only listing present in this evidence set.
The earliest recorded observation for trerjhrdwallet.gitbook.io is 2026-09-15, when it was first observed. An SSL scan on 2026-09-21 identified the certificate issuer as Google Trust Services / WE1. VirusTotal, checked on 2026-09-23, reported 14 detections across 89 scanners. The HTTP check on 2026-10-01 returned status 307, and the resolved IP address 104.18.40.47 is associated with Cloudflare, Inc. in CA.
PhishDestroy, VirusTotal and the HTTP check observed the domain on different dates, so their records describe separate moments rather than one continuous state. The 2026-09-15 first observation predates the 2026-09-21 certificate scan and the 2026-09-23 VirusTotal check, while the 2026-10-01 HTTP response is the most recent dated record here. Because these sources were captured at different times, a reader can compare the sequence of observations but cannot treat any single record as a current description of the domain.
Reviewers should retain the dated records for trerjhrdwallet.gitbook.io, including the PhishDestroy listing and the 2026-10-01 HTTP response, in a form that preserves their original timestamps. Subsequent checks of trerjhrdwallet.gitbook.io should be compared against these earlier observations to identify changes over time. During any review, avoid submitting passwords, wallet credentials or other sensitive information to the domain until its status is independently confirmed.
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.
Edge-IP reputation is not attributed to this domain.
hugh.ns.cloudflare.comLocation describes the IP network.
f3e0d20bcdcb0f6afa89f62c0f4ef0ea0ddd7a7445d5cc7ae8b2e212568ea348gitbook.ioSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_307; http=307; via=https_proxy; location=https://trerjhrdwallet.gitbook.io/us/; server=cloudflare
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
Unknown
probe_inconclusive
Reachable
8 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.
1 community report
CategoryIMPERSONATION
Brand abuse: impersonation, fake affiliation, impersonating Trezor
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
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