VirusTotal
3 / 89
On 2026-10-02, 34314-cdn-satoshilabs.com returned HTTP status 502 in a recorded check. The domain was first observed on 2026-09-08, the same date as its registration date.
Google Safe Browsing flagged the domain on 2026-09-13 with a social engineering threat. VirusTotal recorded 3 detections across 89 scanners on 2026-09-13. OTX showed 2 pulses on 2026-09-13. The domain appeared in the PhishDestroy internal listing, and its registrar is NICENIC INTERNATIONAL GROUP CO., LIMITED.
The HTTP 502 response describes only that recorded request on its date, not the domain's overall content or present availability. The Safe Browsing flag, VirusTotal detections, and OTX pulses are separate source observations that should be read individually rather than merged into a single verdict. The chronology from first observation to the later checks allows a reader to compare dates, but the shared 2026-09-13 dates do not establish simultaneous measurement.
Preserve the Safe Browsing, VirusTotal, OTX, and PhishDestroy records for 34314-cdn-satoshilabs.com. Compare the HTTP response record against the other source records in separate reviews. Use the recorded PhishDestroy listing and the Safe Browsing flag as distinct items when deciding what to monitor next.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='34314-cdn-satoshilabs.com', port=80): Max retries exceeded with url: / (Caused by NewConne
margot.ns.cloudflare.comLocation describes the IP network.
11 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
Phishing: impersonation, fake affiliation, impersonating Trezor
“Phishing: 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