Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
vegaswow.pro was first observed on 2026-10-13, with a recorded PhishDestroy internal listing on the same date. The domain also received a PageSpeed performance score of 87, reflecting a technical measurement of site responsiveness.
Recorded Evidence
VirusTotal checked vegaswow.pro on 2026-10-13, recording 0 detections out of 92 total scanners. The domain was listed internally by PhishDestroy on 2026-10-13. OTX pulses referenced vegaswow.pro twice as of 2026-10-13. Registration was recorded with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-10-10.
Interpretation
The PhishDestroy record for vegaswow.pro contains an internal listing, documenting its inclusion in the publisher's catalogue. VirusTotal provides a quantitative scan result, measuring detections across multiple engines. OTX records reflect external intelligence pulses referencing the domain, offering insight into its visibility in threat intelligence feeds. These sources together provide distinct technical and intelligence perspectives, but each covers different aspects of the domain's profile.
Recommended Actions
For vegaswow.pro, preserve the VirusTotal scan results and PhishDestroy internal listing for future comparison. Review OTX pulse references to monitor any changes in external intelligence records. Maintain a record of the PageSpeed performance score to track technical measurements over time.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 08:21:07 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 08:21:07 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.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
3 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 10:22:37 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 10:22:37 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
security.txt
Reachable (legacy)/.well-known/security.txt
HTTP response
200
Observed at
2026-10-13 10:22:37 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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 08:21:07 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.190.254.
威胁响应 Pipeline
发现
Analysis
Monitoring
7 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
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
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.
(RU)
PhishDestroy Investigation
