vpnmyha.shop was observed in a CryptoFirewall blocklist entry dated 2026-10-13, which records its presence as a listed domain. The domain also received a PageSpeed performance score of 72 on the same date.
Recorded Evidence
CryptoFirewall documented vpnmyha.shop as an external blocklist entry on 2026-10-13. VirusTotal checked the domain on 2026-10-09, recording 19 detections out of 92 total scanners. OTX referenced vpnmyha.shop in 7 pulses as of 2026-10-13. PhishDestroy internally listed the domain, and a PageSpeed check was performed on 2026-10-13 with a score of 72.
Interpretation
VirusTotal contains a detection measurement for vpnmyha.shop, which quantifies how many scanners flagged the domain in its check. CryptoFirewall and OTX provide blocklist and pulse references, respectively, documenting their own criteria for inclusion. The evidence spans several sources, offering a snapshot of technical and security-related observations from multiple dates.
Recommended Actions
vpnmyha.shop should be reviewed against the CryptoFirewall blocklist entry and VirusTotal detection record for ongoing monitoring. Preserve the OTX pulse references and PhishDestroy internal listing for future comparison. These records can be used to track changes in domain status and inform any subsequent analysis or checks.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
IP 평판abuse score 0/1000 reportschecked 2026년 10월 13일
OTX Tagsblocklistbrand impersonationbrowser hijackingbrowser traffic redirectionchrome extensionscryptodns-over-https evasiondrainerfilehashmd5filehashsha1filehashsha256fraudmachineg urlphishdestroy+6 more
HTTP 상태200
기술 세부 정보Provenance & timestamps
최초 발견2026년 10월 13일
Submitted URLhttp://vpnmyha.shop/
TLS 인증서
Certificate hostname mismatch·
발급자 Let's Encrypt / YE2· stored validity ends in 75 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
212.192.14.75
Location describes the IP network.
TLS 인증서
Issuer
Let's Encrypt / YE2
Valid from
2026-09-28 21:46:56
Valid until
2026-12-27 21:46:55
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-13 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint849bf3b4c1316b0022c8f4f6b42bfe4feade32f0f2600a41c063dd30b3f922a7Certificate names · 1 SANs
www.vpnmyha.shop
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 vpnmyha.shop· checked Oct 13, 2026
72
Needs Work
Performance
FCP
3.96s
First Contentful Paint
LCP
4.73s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
29ms
Total Blocking Time
SI
4.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-12 23:34:29 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 212.192.14.75.
위협 대응 Pipeline
발견
Analysis
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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
