The domain aporrojewelry.shop was observed in several security and performance records on 2026-10-07, including a VirusTotal scan and a PageSpeed performance score. Notably, aporrojewelry.shop was also included in the PhishDestroy internal listing on that date.
Recorded Evidence
VirusTotal recorded 0 detections out of 92 scanners for aporrojewelry.shop on 2026-10-07. OTX referenced aporrojewelry.shop in 4 pulses as of 2026-10-07. The domain was present in the PhishDestroy internal listing on 2026-10-07. A PageSpeed performance score of 59 was also documented for this domain on the same date.
Interpretation
These records from VirusTotal, OTX, and PhishDestroy each provide a different perspective on aporrojewelry.shop as of 2026-10-07. VirusTotal's scan did not result in any detections by its participating scanners, while the OTX pulses and PhishDestroy listing indicate that the domain was being tracked or referenced by multiple monitoring sources. The PageSpeed score offers a technical metric for evaluating site performance at that time.
Recommended Actions
For ongoing monitoring of aporrojewelry.shop, retain the VirusTotal scan results, OTX pulse references, and the PhishDestroy listing for future comparison. The recorded PageSpeed performance score should also be preserved as a technical benchmark. Comparing these records over time may help identify any significant changes or new observations related to the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:08:04 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:08:04 UTClast content: 2026-10-11 01:41: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
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
BitDefender
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
넷크래프트
SOCRadar
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of aporrojewelry.shop· checked Oct 7, 2026
59
Needs Work
Performance
FCP
3.03s
First Contentful Paint
LCP
5.62s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
472ms
Total Blocking Time
SI
4.62s
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-06 23:32:37 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.218.
위협 대응 Pipeline
발견
Analysis
Monitoring
10 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.
