us06cloud.live is a blocklisted domain detected by PhishDestroy on 2026-10-21. Risk: critical (90/100). Registrar: NameCheap. Status: Last known active. Hosting: Namecheap. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 24H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.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.
PhishDestroy listed us06cloud.live as a suspicious domain after an admin report highlighted its one‑day age and a page that appears to advertise domain auctions without clear legitimate purpose. The domain was first observed by PhishDestroy on 2026-10-21. A fetch on that date returned HTTP 200 and a chain of alternating HTTP/HTTPS redirects, but no identifiable malicious payload was captured.
How the scam works
Newly registered domains that present generic services are often used as short‑lived fronts to collect credentials or to funnel visitors to later‑stage malicious sites. No such activity was observed on this page, so the risk remains a general possibility rather than a confirmed mechanism.
Evidence
VirusTotal scanned the domain on 2026-10-21 and reported 0 detections out of 92 engines, yielding a clean verdict. Google Safe Browsing also returned a non‑flagged result on the same day. urlscan.io recorded a machine‑learning score of 71 with malicious tags, though its overall verdict was non‑malicious, and OTX listed four pulses referencing the domain; PhishDestroy’s internal blocklist marks it as suspicious while external blocklists showed no entries.
Infrastructure
The domain was registered with NameCheap, Inc. on 2026-10-20 and resolves to the IP address 192.64.119.25, an address owned by NameCheap in the United States. DNS records include standard A, MX, NS and SPF entries, port 80 is open, and DNSSEC is not enabled.
What to do
Visitors should avoid entering credentials, personal data, or cryptocurrency information on the site; if any such data were submitted, change the associated passwords immediately. Defenders can add the exact hostname us06cloud.live to blocklists or monitoring rules and watch for outbound connections to 192.64.119.25. Continue to monitor the domain for any future changes in behavior.
No. PhishDestroy classifies us06cloud.live as a blocklisted domain (risk: critical, 90/100); it was first detected on 2026-10-21. Treat the site as unsafe.
Is us06cloud.live safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on us06cloud.live. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used us06cloud.live?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
RegistrationCreated Oct 20, 2026 (3d · Brand New!)—Expires Oct 20, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 21, 2026
DOM Analysisanalyzed Oct 21, 2026score 90/100
Submitted URLhttp://us06cloud.live/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-23 22:58:06 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 22:58:06 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
5 evidence signal groups linked1 stored notification recordsLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including us06cloud.live)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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)
