How to block Threads on your network
Threads is Meta's text-based social app, launched in July 2023 and closely tied to Instagram. Since April 2025 its web app lives at threads.com.
The tie to Instagram is what makes Threads interesting to block. This guide shows how to remove it cleanly, whether or not Instagram should stay open.
Why organisations block Threads
Threads lands in the same policy discussion as X, Bluesky and Facebook. The reasons differ by setting, but these come up most often.
Student wellbeing
Public replies and quote posts can turn into pile-ons. Schools block social feeds during the day to keep conflicts out of lessons.
Contact from strangers
Open profiles let adults find and reply to young users. Youth organisations block it on networks used by minors.
Distraction
An algorithmic feed is designed to keep people scrolling. Employers and schools block it to protect focus time.
Consistency with Instagram rules
Many schools already block Instagram. Threads uses the same accounts and should be covered by the same decision.
Brand and records
Regulated businesses keep client communication off public social apps, and may restrict posting from company devices.
Age requirements
Meta's apps set minimum ages in their terms. Check the current terms; many primary schools block social apps outright.
Threads domains to block
The two Threads domains are dedicated to the service and safe to block. The content hosts are another matter, because Threads shares them with Instagram and other Meta services.
| Domain or host | Role | Action |
|---|---|---|
threads.com and subdomains | The current web app and the default address since April 2025. | Block |
threads.net and subdomains | The original domain. It now redirects to threads.com, but old links, bookmarks and some app calls may still use it. | Block |
| Shared Meta content delivery hosts | Images and video for Threads, Instagram and other Meta apps. | Only if Instagram goes too |
| Shared Meta login and account hosts | Sign-in and account services used across Meta apps. | Leave open |
| Viewer and proxy sites | Third-party sites that show Threads content without the app. | Category rule |
Shared hosts break other apps. Blocking Meta's shared delivery domains stops Instagram, Facebook and WhatsApp media too. Only do it if your policy blocks all of them anyway. Domain lists change, so confirm in your own logs.
Use the domain category lookup to check any host you find in your logs, and see the social media domains list for how social platforms are grouped.
What admins notice in the logs
Threads traffic can be confusing at first, because so much of it looks like Instagram. These patterns are normal and help you read what you see. Knowing them stops you from adding broad rules that break other apps.
Mixed Meta traffic
A phone with both apps installed talks to shared Meta hosts all day. That alone does not mean Threads is in use; look for the Threads domains themselves.
Redirect hits on threads.net
Old links and bookmarks still point to threads.net. Blocked hits there are expected after the move to threads.com.
Embeds on other sites
News and blog pages can embed Threads posts. Blocked requests from those pages are side effects, not attempts to use the app.
Background refresh
Phones refresh apps in the background. A burst of blocked events overnight from a staff phone is usually that, not active use.
Notification traffic
Push notifications reach phones through the operating system's own services, not through Threads domains. A notification may still appear even though opening the post fails.
Sign-in through Instagram
Users often sign in to Threads with their Instagram account. Seeing account hosts in the log is normal and does not mean the block failed.
Three common scenarios
Most networks fall into one of these. Pick yours, then follow the methods below.
Block Threads, keep Instagram
Typical for offices where marketing uses Instagram but Threads is not part of the plan.
- Block threads.com and threads.net.
- Leave shared Meta hosts open.
- Block the Threads app via MDM on owned devices.
Block both
Typical for schools and youth groups that block social networks for students.
- Block the Social Networking category.
- Add both domain sets explicitly.
- Block both apps via MDM.
Time-based
Typical for workplaces or sixth forms that allow social apps at lunch or after hours.
- Apply the block on a schedule.
- Keep VPN and proxy categories blocked at all times.
- See filtering time schedules.
Methods, layer by layer
Work from the network edge inwards. Each layer adds coverage that the one before cannot provide.
Make the names stop resolving
- Hand out your filtering resolver through DHCP on every network and VLAN.
- Block threads.com and threads.net as wildcards.
- For scenario B, block the Social Networking category too.
- Send all outbound port 53 traffic to your resolver and block port 853.
- No resolver of your own? A managed DNS filter covers this layer.
Check the traffic itself
- Add the domains to a URL filter block profile.
- If your firewall has an application signature for Threads, block it; this helps in scenario A.
- Block QUIC on UDP 443 on filtered segments so the server name is visible.
- Use TLS inspection only where policy allows it, with sensitive categories excluded.
Cover managed laptops anywhere
- Google Admin: add threads.com and threads.net to the URL block list for the right organisational units.
- Microsoft Intune: push an Edge URL block list, or a web content filter for social networking.
- Turn off browser DNS over HTTPS by policy.
Control the app
- On supervised iOS devices, block the Threads app by its identifier or remove it.
- On Android Enterprise, use an approved app list in managed Google Play.
- Push a DNS or content filter profile so rules apply on mobile data.
- Prevent users adding VPN profiles or changing DNS.
For family networks
- Add both Threads domains on the router's website block page.
- Set the router DNS to a filtering resolver so category rules apply too.
- Use a separate profile for children's devices if the router supports it.
The app and the website behave differently
On your Wi-Fi, a DNS block on the Threads domains stops both. Off your Wi-Fi, only managed devices stay covered.
threads.com in a browser
- Blocked on your network by DNS and category rules.
- Blocked anywhere on managed browsers via URL policy.
- Embedded posts on news sites show as blank once blocked.
- Browser encrypted DNS can bypass the network rule unless turned off.
Threads app
- Fails to refresh the feed on your Wi-Fi when the Threads hosts are blocked.
- May still show cached images from shared Meta hosts.
- Works on mobile data unless the device is managed.
- MDM can block install or remove it on owned devices.
Bypass routes and how to close them
A blocked social app tends to produce the same handful of workarounds. Plan for them before you switch the rule on.
VPN apps
Block the VPN / Proxy / Anonymizers category and VPN signatures; stop VPN profiles via MDM. See how to block VPN apps.
Viewer sites
Sites that display public Threads posts without signing in. The Social Networking category is the practical control.
Encrypted DNS
Disable browser DNS over HTTPS, block port 853 and set private DNS on managed Android devices.
Web proxies
Proxy front-ends are renamed constantly; a daily-refreshed proxy category beats a manual list.
Hotspots
Outside any network rule. Device policy and a clear phone policy are the only answers.
Cross-posting
Content from Threads can appear on Instagram. If that matters, it is a scenario B decision.
Test plan
Use a test device configured like a real user's, with mobile data off and a test account signed in.
nslookup threads.com and nslookup threads.net; both should return your block answer.When the block leaks: quick diagnosis
Reports that Threads "still works" usually trace back to one of these causes.
| What the user sees | Most likely cause | Fix |
|---|---|---|
| Old posts visible, nothing new loads | Cached content from shared hosts; the block is working. | No action; explain to the help desk. |
| Everything works on one phone | VPN profile, private DNS or the phone is on mobile data. | Check the phone's settings and MDM group. |
| Works in one browser only | That browser uses its own encrypted DNS. | Turn off browser DNS over HTTPS by policy. |
| Instagram stopped working too | A shared Meta host was blocked in scenario A. | Remove the shared host; keep only Threads domains. |
| A viewer site shows Threads posts | The site is new and not on your list. | Use the Social Networking category; check it in the lookup tool. |
Settings by type of organisation
These are starting points; your own policy and local rules come first. Whatever you choose, keep the VPN and proxy categories blocked so the rule cannot be stepped around.
Primary school
Scenario B everywhere. Block both apps on school tablets. Keep VPN and proxy categories blocked.
Secondary school
Scenario B for students. Staff access is a policy choice; a scheduled rule is a common middle ground.
Office
Scenario A or C. Keep access for the marketing team through a group exception.
Family home
Block on children's devices only, and agree the rule with them first.
Library or youth club
Scenario B on the network used by minors; a lighter adult profile elsewhere.
Guest Wi-Fi
Usually allowed. Block adult, malware and phishing categories as a baseline.
More context: K-12 school web filtering and web filtering software for business.
Decide the policy before the settings
The technical work takes an hour. Agreeing what the rule should be takes longer, and it is what keeps the rule from being undone a month later.
Who and where
- Students only, all staff, or everyone on site?
- School Wi-Fi only, or school devices on any network?
- Guest and BYOD networks included or not?
Who can say yes
- Name one approver for exceptions.
- Prefer group exceptions over individual ones.
- Set an end date and review it.
What happens next
- How are repeat bypass attempts handled?
- Who reads the monthly report?
- When is the rule reviewed again?
Monthly summaries of blocked categories help with the review. See monthly filtering reports for one way to set this up.
What to tell students, staff and parents
A short explanation reduces tickets and workarounds. Keep it plain and honest about what the network can and cannot control.
Students
School Wi-Fi is for learning, social apps are blocked during the day, and using a VPN to get round it breaks the rules. Tell them who to talk to if something online worries them.
Staff
Explain whether staff may use Threads on the staff network, and that school accounts are the only ones to use when posting for the school.
Parents
The school can block Threads on its own Wi-Fi and devices. It cannot block it on a child's personal phone using mobile data; that is a home decision.
Help desk
One standard reply for "Threads is not loading" tickets, with a link to the exception process, keeps answers consistent.
Safeguarding lead
Website category filtering is one layer. Concerns about a particular child go through the school's safeguarding process, not through filter settings.
Managers
In a workplace, tell team leads which groups have access and why, so they can answer questions without raising tickets.
Keep it current with category data
Two domains are easy to maintain by hand. The viewers, scrapers and proxies that grow around a popular app are not, which is where a category rule earns its place.
New domains are checked again after a week and a month, because many add content after launch. Filter vendors and MSPs license the web filtering database to power these rules in their own products. Related guides: how to block Instagram and how to block Bluesky.
Threads blocking FAQ
What domain does Threads use now?
Threads moved its web app to threads.com in April 2025. The older threads.net address redirects there. Block both, each with all subdomains, so old links and bookmarks are covered as well.
Can I block Threads without blocking Instagram?
Partly. Blocking threads.com and threads.net stops the website and most app functions, while Instagram keeps working. Media for both services can come from shared delivery hosts, so do not block those hosts unless you also want Instagram blocked. On managed devices, an MDM app block on Threads alone is the cleanest split.
Why do images still load in Threads after I blocked it?
Images and video are often served from content hosts that Threads shares with Instagram. If the threads.com hosts are blocked, the feed should fail to refresh even if some cached images appear. Check that the app is not using a VPN, private DNS or mobile data.
Does blocking Instagram also block Threads?
Not reliably. A rule on instagram.com does not cover threads.com. If you want both gone, block both domain sets, the shared content hosts, and the Social Networking category.
Can I block Threads on a school iPad or work phone?
Yes. Use MDM to block or remove the Threads app, add threads.com and threads.net to the device web filter, and prevent VPN profiles. This works on mobile data too, unlike a Wi-Fi rule.
How does a category database help block Threads?
Viewer sites, scrapers and proxy pages that show Threads content appear under new names. A Social Networking category refreshed daily catches them without manual list updates.
Social media rules that keep up on their own
For filter vendors, MSPs and edtech makers: 120 million domains in 59 categories, delivered as files that run in your own systems. Starter database tiers from $999; enterprise and OEM licences are quoted per deployment.
Talk to usThreads, Instagram, Facebook and WhatsApp are trademarks of Meta Platforms, Inc. Google, Chrome and Android are trademarks of Google LLC; Apple and iPad of Apple Inc.; Microsoft, Edge and Intune of Microsoft Corporation; other names belong to their respective owners.
These names are used here only to identify the products discussed. Web Filtering Database is not affiliated with, sponsored or endorsed by any of these companies.