PhishDestroy lists 0auth2.1mb.site on its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-19.
How the scam works
The current listing does not identify a specific malicious technique. In general, domains flagged by security engines may be used for phishing, fraud or malware distribution, but no concrete behavior was observed on this site.
Evidence
VirusTotal scanned the domain on 2026-10-03 and reported 8 detections out of 92 engines, including Criminal IP, alphaMountain.ai, Chong Lua Dao, Gridinsoft, Lionic, Seclookup, VIPRE and Webroot. Google Safe Browsing checked the URL on 2026-10-19 and did not flag it. PhishDestroy’s internal blocklist recorded the domain as suspicious on 2026-10-19, while no external blocklists listed it at that time. OTX had zero pulses referencing the domain as of 2026-10-19.
Infrastructure
The recorded IP address for 0auth2.1mb.site is 146.190.2.74, observed on 2026-10-19. No registration, CDN or certificate details are available.
What to do
Visitors who only viewed the site should monitor their accounts for unexpected activity. If any credentials were entered, change the associated passwords immediately. Defenders should add a rule to block or monitor traffic to 0auth2.1mb.site in their security controls.
For the registrable domain 1mb.site behind this subdomain, 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
146.190.2.74
Network ASN
AS14061
Organization
DigitalOcean, LLC
Observed location
Santa Clara, US
Server header
nginx/1.18.0 (Ubuntu)
Nameservers 2
emily.ns.cloudflare.com
terin.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR2
Valid from
2026-09-24 15:43:47
Valid until
2026-12-23 15:43:46
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-19 22:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint93b1f282453a8a5fc32fce9e0972dc180067aa50af5c91e9383108c5fbd938c2Certificate names · 1 SANs
1mb.site
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · 0auth2.1mb.site
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
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 0auth2.1mb.site)
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)
