Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy listed fxgz.cc as a suspicious domain after receiving an admin report noting the site was 161 days old at the time of intake. The prior automated assessment could not determine page content and therefore marked the verdict as unknown. The site returned an HTTP 200 response on 2026-10-22 and the recorded page title is “FXGZ”.
How the scam works
The current evidence does not demonstrate a specific fraud technique; the domain is simply flagged as suspicious. In general, such domains may be used to lure users into providing credentials, personal data, or cryptocurrency information, but no concrete mechanism was observed on this page.
Evidence
VirusTotal scanned the domain on 2026-10-17 (retrieved 2026-10-22) with 92 engines and reported 0 malicious or suspicious detections. Google Safe Browsing checked on 2026-10-22 and did not flag the site. urlscan captured two snapshots on 2026-10-22: the first received a clean verdict, while the second showed a machine‑learning engine score of 99 marked as malicious, though the overall verdict remained non‑malicious. OTX listed three pulses referencing the domain as of 2026-10-22, and PhishDestroy’s internal blocklist marks the domain as blocked while external blocklists reported none.
Infrastructure
The domain was registered with Spaceship, Inc. on 2026-05-14 and is set to expire on 2027-05-14 under a clientTransferProhibited status. The recorded IP was 118.107.59.215, which the registration data listed as belonging to CTG Server Ltd. in Japan, and the domain used Cloudflare nameservers becky.ns.cloudflare.com and conrad.ns.cloudflare.com. TLS was provided by a Let’s Encrypt certificate issued on 2026-10-13, valid until 2027-01-11, employing TLS 1.3 with AES‑256‑GCM encryption.
What to do
Visitors should not submit any login credentials, private keys, or cryptocurrency details to the site; if they have, they should change passwords and secure any wallets. Defenders can block the exact domain fxgz.cc at network perimeters and monitor access logs for requests to the recorded IP address. No wallet approvals or seed phrases were observed, so revocation actions are not required at this time.
RegistrationCreated May 14, 2026 (161d)—Expires May 14, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 0/100
Submitted URLhttp://fxgz.cc/
Favicon Hash
Case ID
Observed page title
FXGZ
TLS Certificate
Issued by Let's Encrypt / YR1· stored validity ends in 80 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
118.107.59.215
Network ASN
AS152194
Organization
CTG Server Ltd.
Observed location
Tokyo, JP
Server header
nginx
Nameservers 2
becky.ns.cloudflare.com
conrad.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR1
Valid from
2026-10-13 09:16:48
Valid until
2027-01-11 09:16:47
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb35c5cb2b1da1d72cae9c22b8d0523ef09841740b6dd97087e2ce826ec1e59fdCertificate names · 1 SAN
fxgz.cc
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
adm.fxgz.ccDomain record
The original observation time is not recorded for these hostnames.
4 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 fxgz.cc)
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)
