VirusTotal
13 / 89 engine detections
보고서 열기“首页”
Security analysis of www.quleo.buzz covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
13 / 89 engine detections
보고서 열기악성
보고서 열기checked — no detections recorded
보고서 열기1 community reference
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
Analysis of www.quleo.buzz, first observed on June 14, 2026, indicates that the domain is currently active and classified as a generic phishing threat with a high risk rating. The domain resolves to the IPv4 address 47.242.217.10 and is hosted on name servers launch1.spaceship.net and launch2.spaceship.net, both associated with the registrar Spaceship, Inc. The registration timestamp aligns with the creation date, confirming a short operational lifespan. Reputation checks show the domain appears on a single security blocklist and is actively blocked by the PhishDestroy feed, reinforcing its malicious intent.
VirusTotal scans have returned detections from two of ninety‑one participating security vendors, providing further corroboration of phishing activity. No additional public intelligence such as Safe Browsing alerts, OTX tags, SSL certificate details, HTTP response codes, or trust‑score metrics is presently available. Consequently, the observable evidence is limited to the blocklist presence, IP resolution, name‑server configuration, registrar information, and the modest VirusTotal detection count.
Defenders should block or sinkhole the IP address 47.242.217.10, add www.quleo.buzz to local deny lists, and monitor the associated name servers for any new resolutions. Continuous re‑scanning with multi‑engine services is recommended to capture any escalation in vendor detections. Organizations employing email filters or web proxies should explicitly deny traffic to this domain while maintaining awareness of potential future variants that may reuse the same registrar or hosting infrastructure.
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.
launch1.spaceship.netlaunch2.spaceship.netLocation describes the IP network.
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.
접속 가능→이용 불가
13/89 engine detections
View sourcePage captured
View source1 community references
View sourceNo threat flag
View sourceduplicate-disabled-373951.invalid
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
duplicate-disabled-373951.invalid
Listed domains receive at least one abuse report; this entry has no retained notification history.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
duplicate-disabled-373951.invalid)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.