Skip to security report
Domain security and threat intelligence
us02live.online favicon

us02live.online

“us02live.online is registered at Namecheap”

Registrar
NameCheap
Resolved IP
162.255.119.245
Registered
Aug 12, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 7/90 Stored blocklist matches: 2 Automated brand label: MetaMask
Sep 3, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 7. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 7 / 90 6 sources

VirusTotal

7 / 90 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer:

Analysis

Critical
VirusTotal
7 / 90
Page captures
2

PhishDestroy threat report

Overview

us02live.online is an impersonation phishing domain that posed as a legitimate service to win visitors' trust. Its listing on the MetaMask and SEAL blocklists points to crypto and wallet users as the audience. PhishDestroy first flagged it on 2026-09-03. The site has been offline since 2026-09-11, and on 2026-10-19 its DNS was still inactive, so the domain no longer resolves.

How the scam works

Impersonation pages copy the look and wording of a trusted brand, then ask for a login, a recovery phrase or a wallet action that hands control to the operator. Anything typed into such a page goes straight to the scammers, and a stolen seed phrase lets them empty a wallet with no further interaction. When it was last checked, the page showed only the title "us02live.online is registered at Namecheap", a default registrar placeholder, which differs from the impersonation content behind our classification.

Evidence

On 2026-09-05, 7 of 90 VirusTotal engines marked the domain as malicious: BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data, Kaspersky, SOCRadar and VIPRE. That is a minority of engines, but the flags come from several unrelated vendors rather than one. Two crypto-focused lists also carry the domain alongside PhishDestroy. MetaMask's blocklist warns wallet users directly, and SEAL is maintained by security responders in the crypto space.

Infrastructure

The domain was registered on 2026-08-12 through NameCheap, Inc., just 22 days before PhishDestroy detected it. It went dark about a week after that, a short lifespan typical of disposable phishing domains. Hosting sat on Namecheap, Inc.'s network in the US, the registrar's own infrastructure, which matches the placeholder page title.

What to do

If you typed a recovery phrase or private key into this site, treat that wallet as compromised. Create a new wallet on a clean device and move any remaining funds there immediately. If you entered a password, change it everywhere you reused it and turn on app-based 2FA. Be wary of anyone who contacts you offering to recover losses, because that is a common follow-up scam. Defenders should block the domain at DNS and proxy level and search logs for visits since 2026-08-12, since a parked domain can come back with new content.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 2 captures

Observed page title
us02live.online is registered at Namecheap
Automated brand references
MetaMask
TLS Certificate
Issued by YE1

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 3, 2026
Registrar NameCheap US(US)
RegistrationCreated Aug 12, 2026 (69d · New) — Expires Aug 12, 2027
Time to First Unavailability 8 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 3, 2026
Submitted URLhttp://us02live.online/
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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
162.255.119.245
Network ASN
AS22612
Organization
Web-hosting.com
Observed location
Los Angeles, US
Server header
nginx/1.28.3 (Ubuntu)

Nameservers 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

Mail routing 5 MX records

  • eforward3.registrar-servers.compriority 10
  • eforward1.registrar-servers.compriority 10
  • eforward2.registrar-servers.compriority 10
  • eforward4.registrar-servers.compriority 15
  • eforward5.registrar-servers.compriority 20

Location describes the IP network.

TLS certificate

Issuer
YE1
Collection time
2026-09-03 10:02:08 UTC
Collection source
PhishDestroy collector

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-19 01:13:35 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-06 22:16:42 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-06 22:16:42 UTC → 2026-09-30 16:14:55 UTC · 569.97h midpoint estimate ≈ 2026-09-18 19:15:48 UTC · precision low · basis bounded
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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 90 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
BitDefender
CRDF
Forcepoint ThreatSeeker
G-Data
Kaspersky
SOCRadar
VIPRE
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
569.97
Estimate basis
Bounded by observations
Estimate precision
Low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history12

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 7
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Reachable→Unavailable

  7. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    7/90 engine detections

    View source
  3. Added to PhishDestroy

    us02live.online

    View source
  4. URLScan

    Page captured

    View source

Lookalike domains

79 stored lookalike domains

Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

us02live.online

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes

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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 us02live.online)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/us02live.online"
  title="PhishDestroy threat report for us02live.online"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>