parik-24.co is referenced in a PhishDestroy internal listing dated 2026-10-13, providing a record of its inclusion in a publisher-owned catalogue. On the same date, the domain achieved a PageSpeed performance score of 100, reflecting a technically responsive web presence.
Recorded Evidence
The domain parik-24.co was first observed on 2026-10-13 and registered with DYNADOT LLC on 2026-08-24. VirusTotal recorded 0 detections out of 92 total scanners for this domain on 2026-10-13. OTX included parik-24.co in 4 pulses as of 2026-10-13. The SSL certificate was issued by Let's Encrypt / YE2 and scanned on 2026-10-13.
Interpretation
PhishDestroy provides a listing record for parik-24.co, documenting its presence in an internal catalogue maintained by the publisher. VirusTotal’s measurement consists of a multi-scanner review for detections, while OTX records the domain’s references in external intelligence sources. These sources together offer a technical and contextual profile of the domain as of their respective observation dates.
Recommended Actions
To support ongoing review of parik-24.co, preserve the PhishDestroy listing and VirusTotal scan record for future comparison. Monitor OTX pulse references and PageSpeed performance scores to identify any changes in the domain’s recorded evidence over time.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-13 06:08:44 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 06:08:44 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.
Google PageSpeed Insights — mobile performance audit of parik-24.co· checked Oct 13, 2026
100
Good
Performance
FCP
1.52s
First Contentful Paint
LCP
1.52s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.82s
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-13 06:08:44 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.58.184.
위협 대응 Pipeline
발견
Analysis
Notifications
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.
OTX Community References
4 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, URLQuery, stored screenshot
2026년 10월 13일
Technical Analysis Recorded
보고서에는 저장된 기술 또는 포렌식 분석 결과가 포함됩니다.
2026년 10월 13일
Sent Report Recorded
Stored outgoing record associated with registrar DYNADOT LLC, 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)
