Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
coin-web3.sbs was documented in a VirusTotal scan on 2026-10-12, where it was recorded with 6 detections out of 92 total scanners. Another notable fact is its inclusion in the PhishDestroy internal listing, providing a publisher-side reference for the domain.
Recorded Evidence
VirusTotal recorded 6 detections out of 92 scanners for coin-web3.sbs on 2026-10-12. The PhishDestroy internal listing included the domain as of 2026-10-13. OTX referenced coin-web3.sbs in 4 pulses on 2026-10-13. The PageSpeed performance score for the domain was 26, recorded on 2026-10-13. The domain was registered with NameSilo, LLC on 2026-09-09.
Interpretation
The PhishDestroy listing contains a publisher-side entry for coin-web3.sbs, documenting its presence in an internal catalogue. VirusTotal’s record provides a quantitative measurement of how the domain was flagged by multiple security scanners. OTX’s pulse count reflects its mention in collaborative intelligence sharing. These records offer a multi-source overview of the domain’s security and performance context as of their respective dates.
Recommended Actions
For coin-web3.sbs, preserve the VirusTotal detection record and the PhishDestroy internal listing for future reference. It is useful to retain the OTX pulse count and PageSpeed performance score for ongoing comparison. Collecting these records will support continued technical review of the domain.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 11:34:15 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 11:34:15 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.
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 11:34:15 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.129.127.
威胁响应 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.
(US)
PhishDestroy Investigation
