The symptom: threads.net looks frozen while Clash is running

You pick a node that works for general browsing, open a new tab, and type or bookmark www.threads.net. The tab title might even update, the address bar looks correct, and sometimes a skeleton flashes—then nothing. Other users describe an infinite spinner centered on an empty page, or a partially painted shell where the timeline never populates. If you disable the proxy briefly, the same account and browser often snap to life, which tempts people to blame “Threads is down” when the service is healthy for everyone else.

That contrast matters diagnostically. A hard outage tends to fail consistently. What looks like “Meta Threads will not open” behind a proxy is frequently partial success: the HTML document or a bootstrap script matched a rule you intended, while companion requests—GraphQL-shaped APIs, static bundles, or media objects—matched a different rule, timed out on a path you did not mean to use, or never entered Clash because DNS went around the core. Modern Meta Threads web is not a single hostname toy; it leans on the same engineering estate as Instagram for sign-in, media, and static delivery. If your profile only mentions threads.net in a casual way without the sibling suffixes, you have described half the product.

This article stays focused on browser behavior and HTTPS-heavy traffic patterns, not on mobile MTProto quirks. If you are comparing checklist shape with other social surfaces on this site, skim Reddit short links and CDN split routing for the same lesson about short domains and asset hosts splitting across rules. The hostname list here is different; the operational habit is the same.

Why proxying only “threads.net” still yields a white screen

People say they “proxied Threads” when they see www.threads.net in a connection log. That is necessary and insufficient. The client downloads JavaScript from hosts that may not use the threads.net registrable domain, pulls media from Instagram CDN namespaces, and talks to APIs whose names evolve with Meta ship velocity. Each hostname is its own TLS connection. Clash selects policy per flow, not per brand in your head, so every new name is a new opportunity to fall through to the wrong group.

Imported community bundles help until they lag a vendor change or classify a CDN label in a way that collides with your personal GEOIP,XX,DIRECT shortcuts. Global CDNs and anycast fronts also confuse naive geography rules: an address associated with a database country may not mean the HTTP semantics you assumed when routing social traffic. The robust fix is the same one we recommend elsewhere: own a small, explicit stack of DOMAIN-SUFFIX lines for the product you care about, ordered ahead of geography guesses, instead of hoping an opaque import stayed current.

Process-level splits still happen. The browser may honor a system proxy while a companion helper uses a different resolver path. TUN mode can mask that gap by steering IP packets without app cooperation, at the cost of integrating with OS firewall stacks and competing VPNs. For rule mechanics shared across guides, keep Clash YAML: routing rules, proxy groups, and Fake-IP at hand while you tune.

Hostnames to pin: threads.net, Instagram auth, and CDN suffixes

Start with the obvious registrable domain: threads.net. A single DOMAIN-SUFFIX,threads.net,THREADS line anchors the product surface so future subdomains Meta adds for experiments stay inside your group without monthly YAML churn. Include it even if your subscription already has a “social” bucket; duplication on purpose beats silent misses after an upstream reorder.

Meta Threads sign-in and account state still walk through Instagram-shaped flows for many users. Practically, you should expect traffic to instagram.com and related subdomains during login, token refresh, and embedded identity UI. A line such as DOMAIN-SUFFIX,instagram.com,THREADS keeps those legs aligned with the same exit characteristics as the main reader experience. If you intentionally isolate Instagram from Threads for household policy reasons, split the groups—but then expect to debug cross-domain failures when the web app cannot complete an OAuth hop.

Static assets and high-volume media frequently appear on cdninstagram.com and the scontent*.cdninstagram.com family that shows up in developer tools when thumbnails hydrate. Cover the registrable suffix first: DOMAIN-SUFFIX,cdninstagram.com,THREADS. When DevTools shows an additional one-off host during a video experiment, add a narrow rule only after logs prove it needs the same treatment as core reading traffic, rather than wildcarding unrelated CDNs and obscuring future debugging.

Some sessions still touch fbcdn.net for certain bundles; that suffix is enormous because it backs broad Facebook surfaces. Referencing it inside THREADS is powerful and blunt: it may pull far more traffic than you meant. Many operators prefer to watch logs for specific fbcdn.net hosts while reproducing Threads-only workflows, then decide whether a dedicated narrower pattern exists or whether a temporary inclusion is acceptable on a test profile. Document what you chose so the next editor knows whether the breadth was deliberate.

Enterprise inspection and campus split-horizon DNS can break SPAs independently of Clash. If only the office Wi-Fi misbehaves, consider policy appliances before you swap exit nodes.

Designing the THREADS policy group

Create a proxy group named THREADS and reference that label from every rule you add for this product. A manual select group is enough if you like deliberate control; add url-test or fallback shapes when several exits are all acceptable for long-lived HTTPS sessions. Keep health-check targets sane so monitoring does not resemble abusive probing.

Resist folding Threads into a catch-all “Western media” bucket unless you truly want identical semantics for unrelated vendors. Separation costs a few YAML lines and buys clarity: when only Threads regresses after a subscription refresh, you adjust THREADS without perturbing unrelated traffic.

A minimal skeleton compatible with mihomo-style cores might look like the following. Replace the placeholder node with your real upstream labels:

proxy-groups:
  - name: THREADS
    type: select
    proxies:
      - <your preferred exit node>
      - DIRECT

rules:
  - DOMAIN-SUFFIX,threads.net,THREADS
  - DOMAIN-SUFFIX,instagram.com,THREADS
  - DOMAIN-SUFFIX,cdninstagram.com,THREADS
  # Optional, high blast radius—confirm in logs before uncommenting:
  # - DOMAIN-SUFFIX,fbcdn.net,THREADS
  # Keep Meta-specific lines before broad GEOIP / MATCH fallbacks

Whether DIRECT belongs inside the group is a policy call. Some operators keep it for controlled testing; others remove it to avoid silent domestic paths. Comment the choice so the profile stays maintainable.

Rule order: place Threads above GEOIP and heavy imports

Clash evaluates rules sequentially and stops at the first match. Profiles tuned for regional performance often insert aggressive GEOIP lines or massive RULE-SET imports. If a bundle swallows a hostname before your personal Meta lines, you lose the game quietly. Shadow critical imports by repeating your suffix block above them; your line wins on first match, and you do not fork upstream files you cannot maintain.

Open any “social media” pack you trust and verify which proxy group it maps Meta labels to. If the classification disagrees with your intent, your explicit lines remain authoritative when placed earlier. For another example of “vendor-specific names before geography,” read split routing for AI sites—different product, identical ordering discipline.

DNS, Fake-IP, and resolver alignment

Fake-IP mode defers final resolution until a rule matches, which is elegant until an application-query path bypasses Clash DNS. For Threads-shaped names, confirm threads.net, instagram.com, and cdninstagram.com resolutions are coherent with your fake-ip-filter and nameserver-policy choices. Mixed resolver strategies can yield different answers for the same qname, which looks like random breakage even when nodes are healthy.

Adjust DNS deliberately when logs show a mismatch: change one knob at a time, reproduce, and record outcomes. Parallel tweaks make postmortems impossible.

On dual-stack networks, inconsistent IPv4 versus IPv6 routing produces intermittent spinners. Align families or disable the path you are not prepared to policy-route under your OS stack.

TUN mode versus system proxy in desktop browsers

System proxy mode works when the browser cooperates. Threads issues parallel requests; TUN pulls more traffic through the core without relying on per-app proxy awareness. The tradeoff is integration overhead with other VPNs and firewalls. On Windows, if enabling TUN creates new symptoms, see Fix Clash TUN on Windows: routing, firewall, and stack conflicts. The domain rules stay constant; only the injection path changes.

Verification: logs first, DevTools second, node swaps last

Reload Threads while watching the live connection panel. You want threads.net, instagram.com, and cdninstagram.com flows mapped to THREADS, not scattered into stale generic groups or DIRECT because a geography shortcut won first. If two related hostnames disagree on exits, fix order or coverage before you declare Meta degraded.

For a quick HTTPS probe through your mixed HTTP port (adjust the port to match your setup):

curl -I --proxy http://127.0.0.1:7890 https://www.threads.net/ 2>&1 | head -20
curl -I --proxy http://127.0.0.1:7890 https://www.cdninstagram.com/ 2>&1 | head -20

TLS success and sane status lines confirm transport-level routing. If curls work but the SPA still stalls, inspect blocking extensions, script errors, and cookie state before you chase YAML.

Browser DevTools network filters are invaluable: sort by blocked or failed rows during the spinner, copy failing hostnames into your suffix list, and retest. That workflow scales better than copy-pasting rumor lists from forums.

Quick symptom map

Intended use

This guide supports lawful routing where you already have permission to reach Meta services. It does not encourage violating terms of service, employer acceptable-use policies, or regional restrictions applicable to you.

Closing: cover threads.net and the CDN legs

Meta Threads frustrations behind Clash rarely require mysticism. They usually come from predictable gaps: treating threads.net as the whole product while Instagram CDNs still wander into GEOIP shortcuts, or letting resolver settings disagree with Fake-IP. Put the suffixes in YAML, keep them above broad geography lines, read the connection log, and expand coverage when DevTools proves a new hostname matters.

Transparent rule matching beats opaque clients for this class of bug: you see which line fired and which group carried the flow, turning a vague “white screen” into a maintainable config. When you want installers and documentation in one place, start from the download page. → Download Clash for free and experience the difference.