Security engines reporting a detection: 1. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Network Security Intelligence Registrar context
Registrar contextNiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
PhishDestroy listed the domain as suspicious after an admin report observed a 204 HTTP response with no visible content. The domain was first seen by PhishDestroy on 2026-10-21, the same day it was registered.
How the scam works
The current evidence does not reveal a concrete fraud technique; the domain is flagged only because newly registered sites that mimic popular brands are often used for credential harvesting, fake exchange offers, or wallet‑approval scams.
Evidence
VirusTotal scanned the domain on 2026-10-21, flagging it as suspicious with one detection (Fortinet labeled it as spam) out of 92 engines. Google Safe Browsing checked the same day and did not flag the domain. External blocklists MetaMask and SEAL listed the domain on 2026-10-21. urlscan.io captured the site on 2026-10-21, returned HTTP 204 and gave an overall clean verdict while its machine‑learning engine assigned a malicious score of 28. OTX reported zero pulses as of 2026-10-21. PhishDestroy’s internal blocklist marks the domain as blocked as of 2026-10-21.
Infrastructure
The domain was registered on 2026-10-21 through NICENIC INTERNATIONAL GROUP CO., LIMITED. It is served via Cloudflare, resolving to IPv4 addresses 188.114.97.1 and 172.67.145.203 and IPv6 addresses 2606:4700:3034::ac43:91cb and 2606:4700:3036::6815:218c. A Let’s Encrypt certificate for *.925825-binance.com is valid until 2027-01-19. DNSSEC is not enabled.
What to do
Visitors should not enter Binance credentials, wallet addresses, or any personal data on this site; if they have, they should change passwords and review account security. Security teams should block the domain at network perimeters, monitor DNS queries for the recorded IPs, and log any access attempts for further investigation. Continue to follow updates from PhishDestroy and other threat feeds for any change in the domain’s behavior.
Issued by Let's Encrypt / YE1· stored validity ends in 89 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.97.1
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
anuj.ns.cloudflare.com
maisie.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE1
Valid from
2026-10-21 02:59:47
Valid until
2027-01-19 02:59:46
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint431f7d34a9ac43dcb1af2e7ec356f84dd33c8b95bb94e8f998729305fab168caCertificate names · 2 SANs
*.925825-binance.com
925825-binance.com
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 · 925825-binance.com
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.
3 evidence signal groups linked0 stored notification recordsLast known active
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.
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 925825-binance.com)
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.
(RU)
PhishDestroy Investigation
