bahe.shop was observed on 2026-10-10 with a recorded entry in the PhishDestroy internal catalogue, and received a PageSpeed performance score of 79 on the same date. The domain was measured by multiple security and technical sources during this period.
Recorded Evidence
VirusTotal checked bahe.shop on 2026-10-10, recording 3 detections out of 92 scanners. OTX referenced the domain with two pulses on 2026-10-10. The domain was registered with Dynadot Inc. on 2026-07-24, and its SSL certificate was issued by Let's Encrypt / YE2, with the certificate scan occurring on 2026-10-10. PhishDestroy contains a dated internal listing for bahe.shop.
Interpretation
PhishDestroy documents bahe.shop in its internal catalogue, providing a record of its inclusion. VirusTotal offers a measurement of detections from external scanners, reflecting a snapshot of security checks. OTX supplies additional intelligence references, while the PageSpeed score describes technical performance. These records allow for comparison across internal and external sources, each with its own measurement scope.
Recommended Actions
For bahe.shop, preserve the VirusTotal detection results and OTX pulse references for ongoing comparison. Retain the PhishDestroy listing as an internal catalogue record. Review the PageSpeed performance score periodically alongside other source records to monitor any changes or new observations related to the domain.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
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 observationLive contentOrdinary HTTP content served90%2026-10-10 23:01:22 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-10 23:01:22 UTClast content: 2026-10-10 23:01:22 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.
Technologies · 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 Previous stored snapshot: 3 detections
alphaMountain.ai
CRDF
Gridinsoft
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of bahe.shop· checked Oct 10, 2026
79
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
4.06s
Largest Contentful Paint
CLS
0.036
Cumulative Layout Shift
TBT
172ms
Total Blocking Time
SI
2.93s
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 05:58:44 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.245.239.201.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
11 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.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · bahe.shop
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches1
Same favicon hash or the same page title as this host.
(US)
