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.
DOM Analysisanalyzed 2026年8月2日score 93/1001 brand signal
Submitted URLhttp://www.quleo.buzz/
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
