VirusTotal
4 / 92 engine detections
보고서 열기“Blueline | Blueline”
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; 40 hours 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.
bluhaven.shop — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Fakeshop; 사기 유형: E Commerce Scam. 증거 요약: VirusTotal 4/92 (alphaMountain.ai, CRDF, Fortinet, Gridinsoft); URLQuery 2 det.; URLScan malicious verdict; Spamhaus DBL_SPAM; PhishDestroy score 95/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
4 / 92 engine detections
보고서 열기2 det.
보고서 열기DBL_SPAM
악성
보고서 열기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
bluhaven.shop is an impersonation phishing page that mimics the Blueline brand, using the page title 'Blueline | Blueline' to deceive visitors. PhishDestroy first identified the domain on 2026-10-18. The site remains active as of 2026-10-18, serving live content designed to trick users into entering sensitive information or downloading malicious software.
Impersonation phishing pages like this one create fake replicas of trusted brands to harvest login credentials, payment details, or install malware. Victims who enter data on the page risk credential theft, financial loss, or device compromise. The page title and branding suggest an attempt to impersonate Blueline, a legitimate entity, to lend false credibility to the scam.
The domain is flagged by 4 out of 92 VirusTotal engines, including alphaMountain.ai, CRDF, Fortinet, and Gridinsoft. urlscan.io has labeled the site as malicious and flagged it as a fake shop, while Spamhaus lists it in their DBL_SPAM database. PhishDestroy has also added it to its blocklist.
The domain was registered on 2026-05-18 through Dynadot Inc. It is hosted on a server with IP 23.252.79.214, operated by Malakmadze Web LLC in Georgia (GE). The TLS certificate was issued by Let's Encrypt under the identifier YE1.
If you visited bluhaven.shop, assume your credentials or data may have been compromised and change passwords elsewhere, especially if reused. Run a malware scan on any device used to access the site. Report the domain to your security team or PhishDestroy for further action. Defenders should block the domain at the network level and update threat intelligence feeds with the provided indicators.
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.
josh.ns.cloudflare.comsarah.ns.cloudflare.comLocation describes the IP network.
3391bafca92e629e820518ba45b6d7e3aa430387c3cfe9727e7d5911b5d84ca0Saved 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 bluhaven.shop · checked Oct 18, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bluhaven.shop/https://bluhaven.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-8Sun, 18 Oct 2026 02:57:21 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
이용 불가→접속 가능
접속 가능→이용 불가
3→4
알 수 없음→live_content
content_served
접속 가능
4 community references
View sourceNo threat flag
View source4/92 engine detections
View sourcePD-20261018-EBAC0B
bluhaven.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bluhaven.shop
PD-20261018-EBAC0B 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 ↗
bluhaven.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
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.