VirusTotal
7 / 92 engine detections
レポートを開く“Blood Records | Blood Records”
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; 2 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.
Amazonなりすまし: bloodrecordsclub.shop — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 7/92 (alphaMountain.ai, CRDF, CyRadar, Fortinet, Gridinsoft); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 92 engine detections
レポートを開くDBL_SPAM
悪意あり
レポートを開くScan report
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
bloodrecordsclub.shop hosts a fake website that pretends to be the Blood Records service. It is designed to lure users seeking medical or health‑related records. The visual design copies the legitimate Blood Records layout, reinforcing the deception. PhishDestroy first detected the domain on 2026-10-17. The site is still active and serving live content as of the last check on 2026-10-19.
The page presents a title “Blood Records | Blood Records” to appear legitimate. Visitors are prompted to enter personal details or login credentials, which are then captured by the attackers. Because the site is a pure impersonation page, no legitimate transaction occurs; the stolen data can be used for identity theft or sold on underground markets. Captured information is typically forwarded to a remote server controlled by the threat actors for later exploitation.
Independent scanners flag the domain as malicious. VirusTotal reports seven detections from 92 engines, including AlphaMountain.ai, CRDF, CyRadar, Fortinet, Gridinsoft, LevelBlue and Webroot. urlscan.io returns a malicious verdict and marks the site as a fake shop. PhishDestroy and Spamhaus list the domain on their blocklists, and OTX has recorded four related pulses. The malicious status was confirmed on 2026-10-19 during routine checks.
The domain’s registrar information is not publicly available. It resolves to IP 23.252.79.136, which belongs to Malakmadze Web LLC in Georgia. The site uses a Let’s Encrypt certificate issued by YE2. The Let’s Encrypt certificate was issued automatically, a common practice for short‑lived phishing sites.
Anyone who entered credentials on bloodrecordsclub.shop should change those passwords immediately and review any associated accounts for suspicious activity. If personal health information was submitted, consider contacting the legitimate Blood Records provider and monitor for identity‑theft signs. Security teams should block the domain at network and email gateways, add it to threat‑intelligence feeds, and monitor for related phishing attempts. Report the phishing site to your email provider and to anti‑phishing organizations such as PhishDestroy.
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.
maleah.ns.cloudflare.commorgan.ns.cloudflare.comLocation describes the IP network.
eeba25572030b6af19cae00c3fce0630335763af5bbd4ace5cc1b4dcaa45fc23Saved 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.bloodrecordsclub.shopDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of bloodrecordsclub.shop · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bloodrecordsclub.shop/https://bloodrecordsclub.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-8Sat, 17 Oct 2026 20:39:27 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.
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
8→7
利用不可→到達可能
到達可能→利用不可
7→8
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source4 community references
View source7/92 engine detections
View sourcePD-20261017-8F1E84
bloodrecordsclub.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bloodrecordsclub.shop
PD-20261017-8F1E84 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 ↗
bloodrecordsclub.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.