ucrpyto.com returned an HTTP status 200 on 2026-10-13, documenting a successful server response on that date. The domain was first observed in records on 2026-10-13, providing a reference point for its initial appearance in available data.
Recorded Evidence
On 2026-10-13, the HTTP status for ucrpyto.com was recorded as 200. The domain appeared on two external blocklists, MetaMask and SEAL, on the same date. VirusTotal checked the domain with 92 scanners and found 0 detections as of 2026-10-13. OTX referenced two pulses for this domain on 2026-10-13. The registrar was recorded as WebNIC, with a registration date of 2026-09-17. The SSL certificate issuer was Let's Encrypt / YE2, and PhishDestroy listed the domain internally on 2026-10-13.
Interpretation
PhishDestroy contains an internal listing for ucrpyto.com, which records its presence in their system on the specified date. VirusTotal’s measurement documents the domain’s status across a wide range of scanners, providing a technical snapshot. OTX pulses offer additional context on community-sourced intelligence. These sources collectively cover technical, reputational, and community-driven aspects, supporting a multi-dimensional review of the domain’s recorded profile.
Recommended Actions
For ucrpyto.com, retain the HTTP status, VirusTotal, and OTX records for ongoing reference. Compare future entries from MetaMask and SEAL blocklists with the current listings to track any changes. Preserve the PhishDestroy internal listing for historical context. Use these dated observations to inform any subsequent checks or reviews of the domain’s security profile.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Google PageSpeed Insights — mobile performance audit of ucrpyto.com· checked Oct 13, 2026
31
Poor
Performance
FCP
17.1s
First Contentful Paint
LCP
18.53s
Largest Contentful Paint
CLS
0.769
Cumulative Layout Shift
TBT
17ms
Total Blocking Time
SI
17.1s
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-12 23:43:03 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
위협 대응 Pipeline
발견
Analysis
Monitoring
7 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월 13일
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026년 10월 13일
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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+
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.
(MY)
