탐지를 보고하는 보안 엔진: 13. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 72H+ 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 domain@abuse.team.
The latest stored availability evidence still shows the domain reachable; 4 days 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.
Elapsed since first report
4 days
Reports sent
1
Latest case ID
PD-20261008-46630F
Current status
HTTP 403 at latest stored check
보고서 요약
parik24-ukraine.com — 연결 가능 · 액세스가 제한됨 (HTTP 403). 브랜드 사칭: Adobe; 사기 유형: Impersonation. 증거 요약: VirusTotal 13/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, Forcepoint ThreatSeeker); Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 98/100. 등록기관: Hosting Ukraine.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
The domain parik24-ukraine.com was first recorded on 2026-10-08 with an OTX pulse and an internal listing in the PhishDestroy catalogue. Its SSL certificate was also scanned on the same date by Let's Encrypt / YR1.
Recorded Evidence
The domain parik24-ukraine.com was registered on 2026-05-03 with Hosting Ukraine LLC. Its SSL certificate, issued by Let's Encrypt / YR1, was scanned on 2026-10-08. OTX reported a pulse for the domain on 2026-10-08, and it was listed internally by PhishDestroy on 2026-10-08.
Interpretation
The OTX pulse and PhishDestroy internal listing provide dated snapshots of parik24-ukraine.com’s status as of 2026-10-08. These records reflect catalogue inclusion and threat intelligence reporting, respectively, without implying content or activity. The SSL certificate scan adds technical context about the domain’s security configuration.
Recommended Actions
Preserve the OTX pulse record and the PhishDestroy internal listing for parik24-ukraine.com to enable future comparisons. Retain the SSL certificate scan results to track any updates to the domain’s security setup. Use these records as reference points for ongoing monitoring.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
DOM Analysisanalyzed 2026년 10월 9일score 98/1004 brand signals
Submitted URLhttps://parik24-ukraine.com/
Favicon Hash
사건 ID
페이지 제목
403 Forbidden - Nginx
Impersonates
AdobeCounter-strikeDota 2League Of Legends
TLS 인증서
Certificate hostname mismatch·
발급자 Let's Encrypt / YR1· stored validity ends in 48 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
185.104.45.48
Network ASN
AS200000
Organization
Hosting Ukraine LTD
Observed location
Kyiv, UA
Server header
nginx
네임서버 3
ns116.inhostedns.com
ns216.inhostedns.net
ns316.inhostedns.org
Mail routing 1 MX record
mx.servicespriority 0
Location describes the IP network.
TLS 인증서
Issuer
Let's Encrypt / YR1
Valid from
2026-09-01 11:41:19
Valid until
2026-11-30 11:41:18
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-08 16:02:30 UTC
Collection source
PhishDestroy collector
Certificate fingerprint76eaac4cdec67fea9774283dc06b380c342fe5b09754928e10d7aa52c268e4efCertificate names · 1 SANs
www.parik24-ukraine.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-13 01:36:16 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 01:36:16 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.
기술 · 1 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Google PageSpeed Insights — mobile performance audit of parik24-ukraine.com· checked Oct 8, 2026
57
Needs Work
Performance
FCP
3.93s
First Contentful Paint
LCP
4.38s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
443ms
Total Blocking Time
SI
8.29s
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-08 15:55:56 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.104.45.48.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
12 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
PDF notice generated Notice text archived (640 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (UA):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and UA's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
(UA)
