onchainex.shop was observed in a PhishDestroy internal listing on 2026-10-09, providing a catalogue entry for the domain on that date. Additionally, a PageSpeed performance score of 65 was recorded, offering a technical perspective on the domain's infrastructure.
Recorded Evidence
PhishDestroy internally listed onchainex.shop as of 2026-10-09. VirusTotal checked the domain on 2026-10-09, recording 0 detections out of 92 total scanners. OTX referenced onchainex.shop in two pulses on 2026-10-09. The PageSpeed assessment on 2026-10-09 provided a performance score of 65.
Interpretation
The PhishDestroy listing contains a publisher catalogue entry, documenting the domain's inclusion as of the recorded date. VirusTotal provides a scan-based measurement, showing how many detection engines flagged the domain during its review. OTX pulses record the domain's appearance in external intelligence sharing, which offers context but does not directly measure content. The evidence presents a technical and intelligence snapshot from multiple sources on 2026-10-09.
Recommended Actions
For onchainex.shop, preserve the PhishDestroy listing and VirusTotal scan records for future reference and comparison. Review OTX pulse entries to monitor changes in external intelligence context. Use the PageSpeed performance score as a technical baseline for later evaluations of the domain's infrastructure.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='onchainex.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
登録情報作成日 2026年9月24日 (17d · Very New!)—Expires 2027年9月24日
技術詳細Provenance & timestamps
初確認2026年10月9日
DOM Analysisanalyzed 2026年10月9日score 80/100
Submitted URLhttp://onchainex.shop/
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:42:23 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 23:01:59 UTClast content: 2026-10-09 23:01:59 UTCcurrent episode first observed: 2026-10-10 20:20:48 UTCobserved RIP window: 2026-10-09 23:01:59 UTC → 2026-10-10 20:20:48 UTC · 21.31hmidpoint estimate ≈ 2026-10-10 09:41:23 UTC · precision medium · 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.
使用技術 · 4 identified
H
HSTS
セキュリティ
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of onchainex.shop· checked Oct 9, 2026
65
Needs Work
Performance
FCP
3.12s
First Contentful Paint
LCP
6.32s
Largest Contentful Paint
CLS
0.047
Cumulative Layout Shift
TBT
60ms
Total Blocking Time
SI
7.35s
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.
Threat First Observed2026-10-09 15:53:43 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.96.1.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
8 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.
ブロックリストの検出
掲載先 2 blocklists: MetaMask, SEAL
2026年10月11日
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月9日
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(US)
