badworkwearofficial.shop was recorded in the PhishDestroy internal listing on 2026-10-10, providing a catalogue entry for the domain. On the same date, PageSpeed measured a performance score of 88 for the domain, which offers insight into its technical configuration.
Recorded Evidence
VirusTotal documented 3 detections out of 92 total scanners for badworkwearofficial.shop on 2026-10-10. OTX recorded 4 pulses for the domain on that date, contributing external intelligence observations. The domain was included in the PhishDestroy internal listing, and PageSpeed measured its performance score as 88. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-10.
Interpretation
The PhishDestroy internal listing contains a catalogue reference for badworkwearofficial.shop, which is a type of publisher-owned record. VirusTotal provides a technical measurement by recording detection counts from multiple scanners, while OTX documents intelligence observations through its pulse records. These sources collectively offer a snapshot of the domain's technical and catalogue status as of 2026-10-10.
Recommended Actions
For badworkwearofficial.shop, preserve the VirusTotal detection record and OTX pulse count for ongoing comparison with future scans. Retain the PhishDestroy internal listing as a reference for catalogue status. Use the PageSpeed performance score to monitor technical changes over time.
DOM Analysisanalyzed 2026年10月10日score 81/1001 brand signal
Submitted URLhttp://badworkwearofficial.shop/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-11 10:00:17 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:00:17 UTClast content: 2026-10-11 10:00:17 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.
技术 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed First positive detection Previous stored snapshot: 3 detections
CRDF
Gridinsoft
Netcraft
网站性能分析
Google PageSpeed Insights — mobile performance audit of badworkwearofficial.shop· checked Oct 10, 2026
88
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
2.89s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
99ms
Total Blocking Time
SI
3.8s
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-10 06:13:18 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.205.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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)
