VirusTotal
15 / 89 engine detections
Open report9ckks83c.fmwqzoq.com is a phishing page detected by PhishDestroy on 2026-08-26. Risk: critical (95/100). Registrar: Cloud DNS. Status: Content unavailable. VirusTotal: 15/89 engines flag it. Do not enter credentials or connect a wallet.
15 / 89 engine detections
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
9ckks83c.fmwqzoq.com is a suspicious domain on the PhishDestroy blocklist. PhishDestroy first saw it on 2026-08-26. No impersonated brand or specific target has been identified. The site went offline on 2026-09-13, and its DNS was still inactive at the last check on 2026-10-19.
No specific scheme has been confirmed for this domain, and no page title or brand ties it to a known campaign. What the evidence does show is a throwaway-looking hostname that a sizeable group of security vendors treat as malicious. Domains in that category typically serve phishing pages, redirect chains to fraudulent offers, or prompts to sign in or connect a wallet. Anyone who reached it should assume that credentials, wallet signatures or payment details entered there could have been captured.
On 2026-09-13, 15 of 89 VirusTotal engines flagged the domain, which is a strong signal for a little-known hostname. The vendors included alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. These are independent engines using different detection methods, so their agreement carries weight. PhishDestroy's own blocklist is the only list that carries the domain.
Both labels, 9ckks83c and fmwqzoq, look machine-generated rather than chosen to resemble any brand. Hostnames like this are cheap to create in bulk and easy to discard, which fits an operation that rotates addresses instead of building a recognisable site. The domain was active for under three weeks after PhishDestroy first saw it. It went dark on the same day the VirusTotal detections were recorded.
If you entered a password on this site, change it wherever you reuse it and turn on two-factor authentication. If you connected a crypto wallet or signed anything, review and revoke token approvals with a trusted approval checker. If you used a seed phrase, move your funds to a new wallet immediately. If you submitted card details, contact your bank. Defenders should block both 9ckks83c.fmwqzoq.com and the parent fmwqzoq.com at DNS and proxy level, and search logs from 2026-08-26 onward for any internal hosts that contacted them.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | f016f857-e8d5-4a8a-a0c1-0a44afc79bb8 |
|---|
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 44,
"malicious": 13,
"suspicious": 1,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"ESET": "suspicious",
"VIPRE": "malware",
"G-Data": "malware",
"Lionic": "phishing",
"Sophos": "malware",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"BitDefender": "malware",
"Chong Lua Dao": "malicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Registrar | Cloud DNS Ltd |
| Created | 2026-08-12T08:15:06Z |
| Expires | 2027-08-12T08:15:06Z |
| Updated | 2026-10-16T15:10:22Z |
| First seen | 2026-08-24T07:49:33Z |
| DNS records | [
{
"ttl": 20,
"type": "CNAME",
"value": "a6c379079327409z.greycdn.net"
},
{
"ttl": 56,
"type": "CNAME",
"value": "dfdcdf8356b74fg.fmwqzoq.com.greycdn.net"
},
{
"ttl": 600,
"type": "CNAME",
"value": "cbf825f055034y.greycdn.net"
},
{
"ttl": 60,
"type": "CNAME",
"value": "dfdcdf8356b74fg.fmwqzoq.com.greycdn.net"
},
{
"ttl": 20,
"type": "A",
"value": "149.104.69.158"
}
] |
| Dns at | 2026-08-24T13:45:59Z |
| Jarm | 2ad2ad0002ad2ad22c42d43d0000003e1c6bdcf3ddc0772f99dffca4dddc83 |
| Certificate | {
"san": [
"fmwqzoq.com",
"*.fmwqzoq.com"
],
"issuer": "ZeroSSL GmbH / ZeroSSL RSA DV SSL CA 2",
"serial": "8705864614521d9a5588a66ffe261adc",
"sha256": "1a1d0b7cc0a0288d042b87545a30982083f5366402f2c584808095177a826b2d",
"subject": "fmwqzoq.com",
"valid_to": "2026-11-10T23:59:59Z",
"valid_from": "2026-08-12T00:00:00Z"
} |
| Registration record | {
"registrar": "Cloud DNS Ltd",
"registrar_iana_id": "4336",
"registrar_url": "https://www.cloudns.net",
"created": "2026-08-12T00:00:00Z",
"updated": "2026-10-14T15:10:54Z",
"expires": "2027-08-12T00:00:00Z",
"status": [
"clientHold",
"clientTransferProhibited"
],
"nameservers": [
"ns1.suspended-domain.com",
"ns2.suspended-domain.com"
],
"dnssec": "unsigned"
} |
No. PhishDestroy classifies 9ckks83c.fmwqzoq.com as a phishing page (risk: critical, 95/100); it was first detected on 2026-08-26. VirusTotal: 15/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on 9ckks83c.fmwqzoq.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
ns1.suspended-domain.comns2.suspended-domain.com1a1d0b7cc0a0288d042b87545a30982083f5366402f2c584808095177a826b2dfmwqzoq.com*.fmwqzoq.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
9ckks83c.fmwqzoq.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Reachable→Unavailable
No threat flag
View source15/89 engine detections
View source9ckks83c.fmwqzoq.com
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
9ckks83c.fmwqzoq.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.