Skip to security report
Domain security report
trerjhrdwallet.gitbook.io favicon

trerjhrdwallet.gitbook.io

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 14/89 Spamhaus DBL: DBL_ABUSED_PHISH Automated brand label: Google
Sep 15, 2026 Google CDN
API
Registrar
Cloudflare
Resolved IP
104.18.40.47
Registered
Mar 30, 2014
0 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
This domain has been flagged as malicious
Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
Spamhaus DBL
DBL_ABUSED_PHISH
VirusTotal
VirusTotal
14 det.
CF Radar
Malicious
TLS Certificate
Expired or unverified
Age
12.6 yr
Observed status
Last known active 307
PhishDestroy
DestroyList
Listed

Source evidence

6 · sources

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.

VirusTotal

14 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_ABUSED_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing

Evidence Summary

Critical
VirusTotal
14/89

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

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.

Read the full analysis3

Recorded Evidence

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.

Interpretation

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.

Recommended Actions

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.

Data coverage & collection14 · datasets with records / 17 · not recorded

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.

Recorded dataPartial recordUTC
VirusTotal
14 / 89 · engine detections
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Spamhaus DBL
DBL_ABUSED_PHISH
Domain registration
Cloudflare, Inc.Collection time not recorded
Network & DNS
104.18.40.47 · 1 · nameserversCollection time not recorded
TLS certificate
Google Trust Services / WE1
Detection & evasion
Stored browser and crawler comparison
Availability history
24 · stored state changes
Source observation history
1 · stored source events
Chainabuse records
1 · recorded reports
IP reputation
Network-level observations
Not recorded in this report 17

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLScan analysis
  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Page captures
  • HTML archives
  • Page analysis
  • Observed indicators
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Wayback archive
Download the dated observations and supporting metadata.
Blocklist records0 · external source matches

Public Blocklist Status

Domain, network & archiveCloudflare, Inc. · 104.18.40.47 · DNS, TLS and retained responses

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Cloudflare US(US)
Registration (base domain)gitbook.io · Created Mar 30, 2014
HTTP Status307 Temporary Redirect
Technical detailsProvenance & timestamps
First DetectedSep 15, 2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.18.40.47
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • hugh.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-14 22:03:00
Valid until
2026-12-13 23:02:54
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-21 04:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf3e0d20bcdcb0f6afa89f62c0f4ef0ea0ddd7a7445d5cc7ae8b2e212568ea348
Certificate names · 1 SANs
  • gitbook.io

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-15 10:07:10 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-15 10:07:10 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-15 10:07:10 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
G-Data
Kaspersky
LevelBlue
Lionic
Netcraft
SafeToOpen
Sophos
VIPRE
Webroot
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checksStored browser and crawler observations
Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No 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
Server header seen by scanner
cloudflare

Scanner note: redirect: raw=redirect_307; http=307; via=https_proxy; location=https://trerjhrdwallet.gitbook.io/us/; server=cloudflare

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & responseCollection history, report status and investigation channels

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.
  1. Threat First Observed 2026-09-21 02:53:11 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive.
Stored observation history25

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 20
  1. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  19. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  20. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
trerjhrdwallet.gitbook.io detected and queued for full analysis
Sep 15, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_ABUSED_PHISH
Sep 21, 2026
Cloudflare Radar Report
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.
VirusTotal
14/89 recorded on VirusTotal
Sep 23, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of Google
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 15, 2026
DestroyList Published
Sep 15, 2026
Monitoring Continues
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Related infrastructureShared hosting, registrar records and related domains
Community recordsRetained community reports and observations

Community intelligence

1 community report

CategoryIMPERSONATION

Brand abuse: impersonation, fake affiliation, impersonating Trezor
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Evidence & External Reports

Third-Party Detection — ChainAbuse
1 report filed for trerjhrdwallet.gitbook.io · category: Impersonation · source checked
Flagged by automated brand-abuse detection on Sep 14, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Deep Analysis
Help & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

1 evidence signal groups linked 0 reports recorded Last 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.

Europol
Find the official reporting channel for your EU country
National police directory
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/trerjhrdwallet.gitbook.io"
  title="PhishDestroy threat report for trerjhrdwallet.gitbook.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>