bbythread.shop returned an HTTP status 301 on 2026-10-12, which is a recorded redirect response. The domain was also first observed on 2026-10-11, providing a recent timeline for its appearance in available records.
Recorded Evidence
On 2026-10-12, the HTTP status for bbythread.shop was recorded as 301. VirusTotal checked the domain on 2026-10-11, documenting 4 detections out of 92 total scanners. OTX included bbythread.shop in 4 pulses as of 2026-10-12. The domain was listed in the PhishDestroy internal catalogue and registered with Dynadot Inc. on 2026-07-04. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-12.
Interpretation
The VirusTotal record contains a scan-based measurement, which documents how many security vendors detected bbythread.shop as noteworthy. OTX provides a count of pulses referencing the domain, reflecting its presence in external threat intelligence sharing. The HTTP status record describes a redirect response, which is a technical observation of the domain’s response at a specific time. The PhishDestroy listing is an internal catalogue entry, adding another layer of recorded evidence for review.
Recommended Actions
For bbythread.shop, retain the VirusTotal, OTX, HTTP status, and PhishDestroy records as part of ongoing monitoring. Compare future VirusTotal and OTX entries with these records to track any changes in the domain's security profile. Review subsequent HTTP status responses to identify shifts in technical behavior. Maintain documentation of all referenced source records for consistent historical analysis.
DOM Analysisanalyzed 2026年10月12日score 81/1001 brand signal
Submitted URLhttp://bbythread.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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 01:35:45 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 01:35:45 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: 4 detections
alphaMountain.ai
CRDF
Gridinsoft
Netcraft
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-12 09:22:20 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 62.233.61.69.
威胁响应 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)
