The domain selena-gomez.us was observed with a PhishDestroy internal listing as of 2026-10-13, documenting its inclusion in a publisher-owned catalogue. Additionally, the domain had a PageSpeed performance score of 56 recorded on the same date, providing a technical metric for its web performance.
Recorded Evidence
VirusTotal checked selena-gomez.us on 2026-10-07, recording 9 detections out of 92 total scanners. OTX pulses referenced the domain three times as of 2026-10-13. The registrar for selena-gomez.us is Web Commerce Communications Limited dba WebNic.cc, with a registration date of 2026-01-20. PhishDestroy internally listed the domain on 2026-10-13, and a PageSpeed performance score was also captured on that date.
Interpretation
PhishDestroy documents the domain’s presence in its internal listing, which is a record of domains catalogued by the publisher for reference. VirusTotal provides a measurement of how many security scanners detected the domain, offering a comparative security context. OTX records the number of times the domain was referenced in its pulses, contributing to the overall intelligence profile. These sources together capture different aspects of the domain’s technical and security-related footprint as of their respective observation dates.
Recommended Actions
For selena-gomez.us, retain the PhishDestroy internal listing and VirusTotal scanner results for ongoing comparison and review. Preserve the OTX pulse references as part of the domain’s intelligence profile. Use the PageSpeed performance score as a technical benchmark for future assessments of web performance or infrastructure changes.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-13 15:21:18 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 15:21:18 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 15:17:42 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
脅威対応 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.
(MY)
