vaultvpn.space was observed in a PhishDestroy internal listing on 2026-10-13, documenting its inclusion in a security monitoring database. The domain also received a high PageSpeed performance score on the same date.
Recorded Evidence
VirusTotal checked vaultvpn.space on 2026-09-26, recording 21 detections out of 92 total scanners. On 2026-10-13, OTX associated the domain with 7 pulses, and CryptoFirewall listed it on an external blocklist. The domain was registered with Registrar of Domain Names REG.RU LLC on 2026-05-20, and its first observation in this dataset was on 2026-10-13.
Interpretation
PhishDestroy provides a record of vaultvpn.space's presence in an internal listing, which documents its status within a security-focused context. VirusTotal's measurement details how the domain was evaluated by multiple scanners, capturing a snapshot of its detection profile. The OTX record contains intelligence pulses, reflecting how the domain has been referenced in threat intelligence feeds. These sources collectively offer a multi-faceted view of the domain's profile across several security monitoring platforms.
Recommended Actions
For vaultvpn.space, retain the VirusTotal, OTX, and PhishDestroy records for ongoing comparison with future data. Review the CryptoFirewall blocklist entry to track any changes in external security listings. Regularly check for updates in these sources to maintain an accurate understanding of the domain's security context.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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 vaultvpn.space· checked Oct 13, 2026
91
Good
Performance
FCP
1.55s
First Contentful Paint
LCP
3.37s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
70ms
Total Blocking Time
SI
2.68s
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:26 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.
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.
(SE)
