cyberpb.xyz was recorded with a PhishDestroy internal listing as of 2026-10-13, and a VirusTotal scan on the same date found zero detections out of 92 scanners. The domain also achieved a PageSpeed performance score of 92, reflecting technical responsiveness at the time of measurement.
Recorded Evidence
PhishDestroy internally listed cyberpb.xyz on 2026-10-13. On 2026-10-13, VirusTotal checked the domain and reported 0 detections from 92 total scanners. OTX pulses were counted at 4 on 2026-10-13. The domain was registered through Atak Domain on 2026-10-08.
Interpretation
VirusTotal provides a scan-based measurement, recording the number of detections from multiple security vendors for cyberpb.xyz. The PhishDestroy listing documents the domain's presence in an internal catalogue, while OTX pulses reflect external intelligence entries. These sources together offer a snapshot of how the domain was referenced and detected by different security intelligence systems on their respective dates.
Recommended Actions
To track changes in the security profile of cyberpb.xyz, preserve the VirusTotal, PhishDestroy, and OTX records for future comparison. Review subsequent scans and listings to identify any new references or detection changes. Use these dated records as a baseline for ongoing monitoring of the domain's security-related observations.
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 13:27:34 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 13:27:34 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
1 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 15:28:30 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 13:27:34 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.183.17.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
2026年10月13日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月13日
Sent Report Recorded
Stored outgoing record associated with registrar Atak Domain, 1 abuse contact
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.
PDF notice generated Notice text archived (808 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (GB):
Computer Misuse Act 1990
Fraud Act 2006
Communications Act 2003 - Section 127
UK law criminalizes unauthorized computer access, fraud, and malicious communications.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(GB)
