ABUSE NOTICE · 24H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 45 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
onchainex.site was observed in the PhishDestroy internal listing as of 2026-10-09, documenting its catalogue status on that date. The domain also received a PageSpeed performance score measurement, providing a technical benchmark for its web infrastructure.
Recorded Evidence
VirusTotal recorded a scan of onchainex.site on 2026-10-09, reporting 0 detections from 92 scanners. OTX documented three pulses for the domain on 2026-10-09. The domain’s registration with NAMECHEAP INC is dated 2026-02-24. PhishDestroy’s internal listing was noted as present on 2026-10-09, and the PageSpeed performance score was measured at 56.
Interpretation
PhishDestroy contains a listing for onchainex.site, which documents its catalogue entry and status for internal reference. VirusTotal’s scan provides a measurement of detection results from multiple security engines, while OTX pulses serve as external intelligence indicators. These records together offer a technical snapshot of the domain from several perspectives.
Recommended Actions
For onchainex.site, retain the VirusTotal scan results and OTX pulse records for future comparison and monitoring. Preserve the PhishDestroy internal listing as a reference for catalogue status. Use the PageSpeed performance score as a technical benchmark for subsequent assessments.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='onchainex.site', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
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:13 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 16:39:50 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 16:39:50 UTC → 2026-10-09 20:20:42 UTC · 3.68hmidpoint estimate ≈ 2026-10-09 18:30:16 UTC · precision high · 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.site· checked Oct 9, 2026
56
Needs Work
Performance
FCP
8.63s
First Contentful Paint
LCP
11.33s
Largest Contentful Paint
CLS
0.047
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
8.63s
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:37 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.96.1.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
9 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
3 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, URLQuery, stored screenshot
2026年10月9日
Technical Analysis Recorded
レポートには、保存されたテクノロジーまたはフォレンジック分析の結果が含まれます。
2026年10月11日
Sent Report Recorded
Stored outgoing record associated with registrar NAMECHEAP INC, 1 abuse contact
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)
