Cloudflare Radar
悪意あり
レポートを開く“BJ's PJ's | Organic Cotton Pyjamas”
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; 3 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.
bjspjsshop.shop — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 0/92; URLScan malicious verdict; CF Radar malicious; PhishDestroy score 73/100. レジストラ…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
悪意あり
レポートを開く悪意あり
レポートを開く0 / 92 engine detections
レポートを開くScan report
レポートを開く4 community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
bjspjsshop.shop presents itself as "BJ's PJ's | Organic Cotton Pyjamas", a boutique sleepwear store aimed at people shopping online for natural-fibre nightwear and gifts. PhishDestroy classifies it as an E-Commerce Scam, a fake online shop, and first flagged it on 2026-10-16. The site was still online and serving its storefront when last checked on 2026-10-19.
Fake shops like this copy the look of a small, ethical clothing brand. They pair soft product photos with organic-cotton claims and steep discounts that make a quick checkout feel safe. The shopper pays, then receives nothing, a cheap item unlike the listing, or a stream of excuses about shipping delays. The checkout also collects names, addresses, phone numbers and card details, which can be reused for further fraud or targeted phishing.
urlscan.io rates the site malicious and specifically marks it as a fake shop, which is the strongest independent signal here. VirusTotal shows 0 of 92 engines flagging it as of 2026-10-16. That gap is common with scam storefronts, which host no malware and simply take money, so antivirus vendors tend to miss them. The domain is referenced in 4 AlienVault OTX threat pulses, and PhishDestroy is currently the blocklist carrying it.
The domain was registered through Spaceship, Inc. on 2026-03-26, roughly seven months before PhishDestroy detected it. That lead time is consistent with a storefront being set up and run quietly before reports accumulated. It is hosted on Malakmadze Web LLC's network in Georgia, which is a mismatch for a shop presenting itself as a homely pyjama label. Its Let's Encrypt certificate shows a padlock in the browser, but it only encrypts the connection and says nothing about whether the seller is honest.
If you ordered from this site, contact your card issuer or bank now, report the transaction as fraud and request a chargeback. Keep any order confirmations and emails as evidence. If you paid by bank transfer, gift card or crypto, report it to your bank and local fraud authorities quickly, because those payments are hard to recover. Watch for follow-up emails or calls about "delivery problems" or refunds that ask for more payment or personal details. Security teams and payment providers should block bjspjsshop.shop, flag merchant activity linked to it, and report the storefront to the registrar and hosting provider for takedown.
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.
amos.ns.cloudflare.commillie.ns.cloudflare.comLocation describes the IP network.
fd059a9045dbed8171b9ca7a164a9c2c57968abfcb9f765e6d288afbb874480dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
img.bjspjsshop.shopDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of bjspjsshop.shop · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bjspjsshop.shop/https://bjspjsshop.shop/Cache-Control: private, no-cache, no-store, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8summary_large_imageh3=":443"; ma=2592000private, no-cache, no-store, max-age=0, must-revalidategziptext/html; charset=utf-8Fri, 16 Oct 2026 19:31:08 GMT; rel=preload; as="style"strict-origin-when-cross-originchunkedRSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch, Accept-Encoding1.1 CaddynosniffSAMEORIGIN1; mode=blockValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy
bjspjsshop.shop
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
不明→live_content
content_served
利用不可→到達可能
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
利用不可→到達可能
到達可能→利用不可
到達可能
No threat flag
View source4 community references
View source0/92 engine detections
View sourcePD-20261016-D299C7
bjspjsshop.shop
View sourcePage captured
View sourcePD-20261016-D299C7 Recipient: abuse@rashost.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
bjspjsshop.shop)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.