The domain bbirdgshop.shop returned an HTTP status of 200 on 2026-10-12, documenting a successful response at that time. Additionally, the domain was observed in the publisher-owned PhishDestroy internal listing, providing another recorded reference for review.
Recorded Evidence
VirusTotal checked bbirdgshop.shop on 2026-10-11, recording 9 detections out of 92 scanners. OTX pulses were documented at 4 on 2026-10-12. The domain was first observed on 2026-10-11, and its registration date is listed as 2026-05-22. The PageSpeed performance score was measured at 88 on 2026-10-12.
Interpretation
The VirusTotal record contains a scanner-based measurement of detections for bbirdgshop.shop, offering insight into how multiple sources evaluated the domain. The PhishDestroy internal listing documents a catalogue entry, which is a publisher-owned reference for internal review. These records provide a timeline of observations from different sources, allowing for comparison of technical and security-related data.
Recommended Actions
For bbirdgshop.shop, preserve the VirusTotal, OTX, and PhishDestroy records for ongoing review and comparison. Use the HTTP status and PageSpeed performance score as technical references in future assessments. Maintain a separate record of each source's observations to support any subsequent analysis of the domain's history and profile.
DOM Analysisanalyzed 2026年10月12日score 88/1002 brand signals
Submitted URLhttp://bbirdgshop.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-13 01:35:47 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 01:35:47 UTClast content: 2026-10-13 01:35:47 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: 9 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
G-Data
Gridinsoft
LevelBlue
Netcraft
网站性能分析
Google PageSpeed Insights — mobile performance audit of bbirdgshop.shop· checked Oct 12, 2026
88
Needs Work
Performance
FCP
2.87s
First Contentful Paint
LCP
2.87s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
120ms
Total Blocking Time
SI
3.72s
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-12 09:22:24 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.245.239.152.
威胁响应 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)
