Skip to security report
Domain security and threat intelligence
0q.hk favicon

0q.hk

In short

0q.hk is a MetaMask impersonation page detected by PhishDestroy on 2026-10-08. Risk: critical (95/100). Registrar: Alibaba Cloud Computing. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 6/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“灵趣绘刻 | ChatGPT Image 2 中文 AI 文生图与改图平台 · 4K 高清”

Registrar
Alibaba Cloud Computing
Resolved IP
188.114.96.3
Registered
Apr 20, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 6/92 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: MetaMask
OTX: 4 refs Oct 8, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 6 / 92 · OTX 4 references 6 sources

VirusTotal

6 / 92 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 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.

Analysis

Critical
VirusTotal
6 / 92
OTX
4 community refs
Page captures
4

PhishDestroy threat report

Overview

0q.hk presents itself as 灵趣绘刻, a Chinese-language "ChatGPT Image 2" text-to-image and photo-editing service promising 4K output. It borrows the ChatGPT name to look like an official or authorized gateway, and its audience is Chinese-speaking users who want image generation. PhishDestroy classifies it as an impersonation phishing page and first saw it on 2026-10-08. The site was still online and serving content on 2026-10-19.

How the scam works

Fake AI front-ends like this attract people with a famous product name and a ready-made interface, then ask for something of value before any output is delivered. That is usually a sign-up with an email and password, a login that reuses existing account credentials, or a payment for credits or a subscription. Whatever the visitor enters goes to the operator. The page title describes a working image tool, and the site is classified here as impersonation phishing because it trades on the ChatGPT brand.

Evidence

Six of 92 VirusTotal engines flagged the domain as of 2026-10-15: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a modest count, so many security products may still let the page load. Stronger backing comes from elsewhere. Spamhaus lists the domain in its DBL under the phishing category. MetaMask and SEAL block it alongside PhishDestroy, which shows that crypto-focused defenders treat it as a threat. Four AlienVault OTX pulses also reference it.

Infrastructure

The domain was registered through Alibaba Cloud Computing Ltd. on 2026-04-20, about five and a half months before PhishDestroy detected it. That gap leaves room for an operator to age the domain or build traffic before it attracts attention. The site sits behind Cloudflare, with an edge address that geolocates to Canada, so the origin server is not visible. It uses a free Let's Encrypt certificate, and the padlock in the browser says nothing about whether the site is legitimate.

What to do

If you created an account on 0q.hk, change that password everywhere you have reused it. Turn on two-factor authentication for your real OpenAI and email accounts. If you paid for credits or a subscription, contact your card issuer or payment provider to dispute the charge and block further billing. Use OpenAI's own apps or authorized resellers rather than third-party "ChatGPT" portals. Defenders should block the domain at DNS and proxy level and add it to mail and web filters, since current vendor coverage is thin.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-08T00:19:34Z

Observed: · Retrieved:

Uuid
01a118e0-eea2-741f-87a8-9e287d0a7783
Final url
https://0q.hk/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://0q.hk/",
        "from": "http://0q.hk/",
        "status": 307
    }
]
Ip
104.21.80.132
Contacted domains
[
    "cms-assets.youmind.com",
    "raw.githubusercontent.com",
    "github-production-user-asset-6210df.s3.amazonaws.com",
    "github.com",
    "challenges.cloudflare.com",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "185.199.109.133",
    "52.217.91.104",
    "4.237.22.38",
    "104.18.22.146",
    "104.16.79.73",
    "104.18.94.41",
    "104.21.80.132"
]
Asns
[
    "54113",
    "16509",
    "8075",
    "13335"
]
Countries
[
    "US",
    "AU"
]
Document hash
90acaac4aeb4a5adf0e7fe4551148de06aed06c55b380ff9caa4223c0ae77960
Script hashes
[
    "78aaaf9c40c9edb9dcb7e1a416b8544cab3a24b50c13a41bc942b91c579f28ea",
    "f47be93295968610723c2d05ee7e979afdb6a3e80ee839a4c3c0ded92b6c47f5",
    "0768960466096582aa9836e5175d66021b382816df1bccbc723161a6dcc60f45",
    "04704baef149c2bb2778be769870a065266555d69bfc714df72b22af3720f235",
    "eaaf3b63df30d165a0c5abb64e8e07f5e725b57ae9a024f5e5dacd7d854238d5",
    "114dab1aa2d64ff45829f3fec63d071c561455711db5efba74f33ea50e189fc9",
    "89acd401ad07146ee34e2b9b4f51740494f50882863a4dc9101ddb6b8592bd4a",
    "7e87c37c9d8d326a3cb0c3d7f32b8852aaef161591d66e75652a2c73bcdf83e5",
    "4dc065e441ac69d8838fe67abf801b7e47ef47c265d4a99673136d93123f48b4",
    "75a4237e1151739900ebd07a95e609dafd12e68c5ef57483b7285c3646aca8e2"
]
Globals
[
    "webpackChunk_N_E",
    "__next_f",
    "__cfBeacon",
    "next",
    "_N_E_STYLE_LOAD",
    "turnstile",
    "MotionIsMounted"
]
Cookies
[
    "server_name_session"
]
Storage keys
[
    "zq-landing-intro-v2"
]
Tls
{
    "san": [
        "*.0q.hk",
        "0q.hk"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "0q.hk",
    "protocol": "QUIC",
    "valid_to": "2026-12-07T01:47:59Z",
    "valid_from": "2026-09-08T01:48:00Z"
}
Domain age days
157
Apex age days
157
Tls age days
29
Tls valid days
89
Requests
77
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "Next.js"
}
Cloudflare Radar · 2026-10-08T00:22:50Z

Observed: · Retrieved:

Uuid
1084220b-ca96-4227-ab97-0ceb183aeea8
Final url
https://0q.hk/
Status
200
History
[
    {
        "url": "https://0q.hk/",
        "status": 200
    }
]
DOM structure hash
177443bfff79a2b42a114890d905df14092b6290f13aa505f408bac48da1cbac
Document hash
90acaac4aeb4a5adf0e7fe4551148de06aed06c55b380ff9caa4223c0ae77960
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "0q.hk",
        "type": "A",
        "value": "104.21.80.132"
    },
    {
        "name": "0q.hk",
        "type": "A",
        "value": "172.67.182.106"
    },
    {
        "name": "0q.hk",
        "type": "AAAA",
        "value": "2606:4700:3034::6815:5084"
    },
    {
        "name": "0q.hk",
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:b66a"
    }
]
Dnssec valid
false
Ip
104.21.80.132
Registration record
{
    "registrar": "Alibaba Cloud Computing Ltd.",
    "created": "2026-04-20T00:00:00Z",
    "expires": "2027-04-20T00:00:00Z",
    "nameservers": [
        "carlos.ns.cloudflare.com",
        "diva.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-20T02:55:28Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-05-03T12:31:52Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.182.106"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:b66a"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 include:_spf.mx.cloudflare.net ~all"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "carlos.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.80.132"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "route1.mx.cloudflare.net",
        "priority": 1
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "route3.mx.cloudflare.net",
        "priority": 3
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "diva.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "carlos.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "route2.mx.cloudflare.net",
        "priority": 2
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:5084"
    }
]
Dns at
2026-10-20T03:08:10Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.0q.hk",
        "0q.hk"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "55b7b3c5a301de9eb7ac34e557f6299dd71",
    "sha256": "5463e06a0fba49e6c8a2827d6fdd28f0bef1319545a34c1f8ca82b1115126254",
    "subject": "0q.hk",
    "valid_to": "2026-12-07T01:47:59Z",
    "valid_from": "2026-09-08T01:48:00Z"
}
Registration record
{
    "status": [
        "Active"
    ]
}

Questions about 0q.hk

Is 0q.hk legit?

No. PhishDestroy classifies 0q.hk as a MetaMask impersonation page (risk: critical, 95/100); it was first detected on 2026-10-08. VirusTotal: 6/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is 0q.hk safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on 0q.hk. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used 0q.hk?

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.

Explore

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

Last checked

Stored Capture · 4 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Alibaba Cloud Computing
RegistrationCreated Apr 20, 2026 (185d) — Expires Apr 20, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 8, 2026
DOM Analysisanalyzed Oct 9, 2026score 95/1003 brand signals
Submitted URLhttp://0q.hk/
Favicon Hash
Observed page title
灵趣绘刻 | ChatGPT Image 2 中文 AI 文生图与改图平台 · 4K 高清
Automated brand references
Chatgpt Openai YouTube
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 45 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • carlos.ns.cloudflare.com
  • diva.ns.cloudflare.com

Mail routing 3 MX records

  • route1.mx.cloudflare.netpriority 1
  • route2.mx.cloudflare.netpriority 2
  • route3.mx.cloudflare.netpriority 3

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-08 01:48:00
Valid until
2026-12-07 01:47:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 10:02:21 UTC
Collection source
PhishDestroy collector
Certificate fingerprint5463e06a0fba49e6c8a2827d6fdd28f0bef1319545a34c1f8ca82b1115126254
Certificate names · 2 SANs
  • *.0q.hk
  • 0q.hk

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-22 10:31:02 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 10:31:02 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:31:02 UTC last content: 2026-10-22 10:31:02 UTC
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 · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 2 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
VIPRE

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of 0q.hk · checked Oct 8, 2026

70
Needs Work
Performance
FCP
1.98s
First Contentful Paint
LCP
8.4s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
42ms
Total Blocking Time
SI
5.2s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history21

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unavailable→Reachable

  4. Availability monitor · Recorded state

    Reachable→Unavailable

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 16
  1. Availability monitor · Recorded state

    Unavailable→Reachable

  2. Availability monitor · Recorded state

    Reachable→Unavailable

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unavailable→Reachable

  8. Availability monitor · Recorded state

    Reachable→Unavailable

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unavailable→Reachable

  12. Availability monitor · Recorded state

    Reachable→Unavailable

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  16. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/92 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Added to PhishDestroy

    0q.hk

    View source
  5. 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.

0q.hk

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Last 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.

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 0q.hk)
  • 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/0q.hk"
  title="PhishDestroy threat report for 0q.hk"
  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>