beingly.shop was recorded in a PhishDestroy internal listing as of 2026-10-13, providing a dated reference for its inclusion in a security catalogue. The domain also received a high performance score from a PageSpeed check on the same date.
Recorded Evidence
OTX recorded three pulse entries for beingly.shop on 2026-10-13. VirusTotal checked the domain on 2026-10-11 and documented 5 detections out of 92 total scanners. A PageSpeed performance score of 89 was also recorded on 2026-10-13. PhishDestroy listed the domain internally as of 2026-10-13.
Interpretation
PhishDestroy provides a record of beingly.shop in its internal listing, which documents the domain's presence in a security-focused catalogue. VirusTotal's measurement consists of a scan by multiple engines, recording the number of detections and total scanners. OTX references pulse entries, which are external security intelligence contributions, offering another perspective on the domain's observation history. These sources collectively represent different types of technical and intelligence-based records for the domain.
Recommended Actions
For beingly.shop, retain the PhishDestroy internal listing and VirusTotal scan records for ongoing reference and comparison. Review OTX pulse entries to monitor any changes or new intelligence related to the domain. Use the PageSpeed performance score as a technical benchmark for future assessments of the domain's infrastructure.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 04:47:35 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 04:47:35 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.
Last analyzed Previous stored snapshot: 5 detections
CRDF
G-Data
Gridinsoft
LevelBlue
Netcraft
网站性能分析
Google PageSpeed Insights — mobile performance audit of beingly.shop· checked Oct 13, 2026
89
Needs Work
Performance
FCP
2.97s
First Contentful Paint
LCP
2.97s
Largest Contentful Paint
CLS
0.009
Cumulative Layout Shift
TBT
46ms
Total Blocking Time
SI
3.36s
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-13 04:47:35 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 37.72.142.130.
威胁响应 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.
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.
