Analysis of www.trzn.market was performed on 24 July 2026. The site returns HTTP 200 and serves a page whose title is “TorZon Market Link — Official Darknet URL”. Technical fingerprinting shows the site is hosted on Netlify with HSTS enabled and is fronted by Cloudflare (AS13335) from a US location, resolving to 172.67.138.62. The domain was registered on 23 February 2026 through Key‑Systems, LLC and uses the ns1/ns2 p08.nsone.net name servers.
The TLS certificate is issued by Let’s Encrypt (R12) and is currently valid. Threat intelligence flags the domain as a wallet/seed phishing operation that impersonates the brand “across”. Gridinsoft assigns a trust score of 0 out of 100, indicating extreme suspicion. VirusTotal analysis shows that 2 of 93 scanning engines have flagged the domain, and the domain appears on a single external blocklist maintained by PhishDestroy.
No additional public intelligence such as OTX references or Safe Browsing alerts were observed. The combination of a recent registration, low trust score, active TLS, and detection by multiple vendors suggests the domain is actively used for credential or seed harvesting. Defenders should block the domain at network perimeter, add it to internal phishing blocklists, monitor DNS queries for the associated IP and name‑servers, and consider issuing user warnings about the “across” brand impersonation. Ongoing observation is required to determine whether the site hosts additional payloads or evolves its infrastructure.
DOM Analysisanalyzed 2026年4月23日score 81/1003 brand signals
Submitted URLhttps://www.trzn.market/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
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.
Certificate fingerprint30cc9f78003f31401bbd889810e49b4376c1b066b141f647d216e60ecdbeb7f2Certificate names · 2 SANs
link.trzn.market
trzn.market
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:16:04 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:16:04 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.
使用技術 · 2 identified
N
Netlify
PaaSCDN
Platform for deploying and hosting modern web applications.
H
HSTS
セキュリティ
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of trzn.market· checked Apr 29, 2026
93
Good
Performance
FCP
1.76s
First Contentful Paint
LCP
1.81s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.95s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
11 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
(DE)
