Best privacy-focused providers
Usenet with SSL: why port 563 matters
Short answer
SSL stops your internet provider and anyone on your network from reading your login and the articles you download, which plain port 119 sends as readable text. With Newshosting, for example, you connect to news.newshosting.com on port 563 with SSL switched on. Your Usenet provider still sees your account and what you download.
Port 563 is the encrypted Usenet port, and that is the whole reason it matters. On port 119 your download client sends your password, its commands and the article IDs as readable text. On port 563 the same traffic travels inside TLS, so your internet provider and anyone on your Wi-Fi can only see that you are connected to a news server and how much data is moving.
Who can see what
| Who | Port 119, no SSL | Port 563 with SSL | Port 563 with SSL and a VPN |
|---|---|---|---|
| Your internet provider | Server, login, article IDs and content | That you connect to a news server, and how much data | That you connect to a VPN, and how much data |
| Others on the same Wi-Fi | Same as your internet provider | Server and amount of data | VPN and amount of data |
| The VPN company | Not involved | Not involved | That you connect to a news server, and how much data |
| Your Usenet provider | Account, IP and articles requested | Account, IP and articles requested | Account, VPN IP and articles requested |
Notice that the bottom row stays the same in every column. SSL protects the route to the server, not the server itself, because your provider has to know which articles you want before it can send them.
Your password is the first thing SSL protects
Your client logs in at the start of every connection, so with 50 or 100 connections open it logs in 50 or 100 times. On port 119 every one of those logins crosses the network in plain text, and on a shared or public network that is the easiest thing for someone to grab. If you have ever run on port 119, move to 563 and change your Usenet password while you are at it.
A bundled VPN does not replace SSL
A fair number of providers throw in a VPN. In our data, checked 2026-10-23, Newshosting, Easynews and UsenetServer bundle PrivadoVPN, Giganews bundles VyprVPN, Eweka and TweakNews include a VPN, Pure Usenet includes one for up to 10 devices, and XLned adds one free on annual plans. A VPN does hide your traffic from your internet provider. But without SSL, the VPN company can read your Usenet traffic in its place. So keep SSL on for the news server and treat the VPN as a bonus for everything else you do online. Usenet without a VPN explains when you can do without it.
Checking that SSL is actually on
- Open the server settings in your download client. The port should say 563 and the SSL or encryption option should be switched on.
- Press the test button. If the test passes on 563 with SSL, the encrypted connection works.
- Look for old servers in the list. A forgotten entry on port 119 can still fetch articles if it is enabled.
- Open your indexer's site over HTTPS. That is a separate connection, and SSL on the news server does nothing for it.
Usenet SSL port 563 setup goes through every field and lists hostnames for 15 providers. For a Newshosting account it boils down to news.newshosting.com, port 563, SSL on.
What SSL leaves alone
Encryption has no effect on retention, completion or takedown rules. A post removed under DMCA or NTD (the US and Dutch takedown procedures) is gone whether you connect encrypted or not. SSL also does not make you anonymous to your provider or your indexer. If privacy features are what you are shopping for, best privacy Usenet compares providers on exactly that.
FAQ
- Is there any reason to use port 119 today?
- Only as a quick test when SSL fails and you want to know whether the port or the login is the problem. Go back to 563 straight after.
- Does SSL slow downloads?
- Not in any way you would notice on current hardware. Your connection count and line speed make a much bigger difference.