VirusTotal
11 / 92 engine detections
Open report“BAGGY | BAGGY”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rashost.com.
The latest stored availability evidence still shows the domain reachable; 9 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
11 / 92 engine detections
Open reportMalicious
Open reportScan report
Open report4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
baghause.shop is an impersonation phishing page dressed up as a bag retailer under the name "BAGGY". It targets online shoppers looking for discounted bags and accessories. PhishDestroy first flagged it on 2026-10-10, and as of 2026-10-19 the site was still online and serving its storefront.
The page, titled "BAGGY | BAGGY", copies the look of a legitimate fashion shop. It uses product listings and attractive prices to steer visitors to checkout. Sites like this typically collect names, delivery addresses, email addresses and full card details at the payment step. The victim then either receives nothing or receives a cheap substitute, and the stolen card data can be reused or sold. The page presents itself as an ordinary retail brand storefront, while PhishDestroy classifies it as impersonation phishing.
urlscan.io rates the site malicious and specifically identifies it as a fake shop, which matches our classification. On VirusTotal, 11 of 92 engines flagged the domain as of 2026-10-15, including BitDefender, ESET, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, Gridinsoft and LevelBlue. That count is modest, but it comes from several unrelated vendors. The domain also appears in 4 AlienVault OTX threat pulses, showing that other researchers are independently tracking it.
The domain was registered through Dynadot Inc. on 2026-06-05, roughly four months before we detected it. That gap suggests it was either kept in reserve or operated quietly before drawing attention. It is hosted on the Malakmadze Web LLC network in the United States. Its free, automatically issued Let's Encrypt certificate gives it a padlock, which says nothing about whether the shop is genuine.
If you placed an order, contact your card issuer immediately to block the card, dispute the charge and request a replacement. Do not pay any follow-up "customs" or "shipping" fees that the shop requests. If you created an account there, change that password anywhere you reused it. Expect targeted phishing emails at the address you used, and treat any message about your "order" with suspicion. Defenders should block the domain at the DNS and proxy level and add it to e-commerce fraud filters.
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.
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.
arely.ns.cloudflare.comjoel.ns.cloudflare.comLocation describes the IP network.
1e6d024e46c2f2d3db97100451107416f57fda1b26ad744411521eb63fa3e506Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of baghause.shop · checked Oct 10, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable→Unavailable
Unknown→live_content
content_served
Unavailable→Reachable
Reachable→Unavailable
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unavailable→Reachable
Reachable→Unavailable
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Reachable
No threat flag
View source11/92 engine detections
View source4 community references
View sourcePD-20261010-6F3146
baghause.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
baghause.shop
PD-20261010-6F3146 Recipient: abuse@rashost.com If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
baghause.shop)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.