We operate a public Matrix homeserver, anyone can sign up and use it as they like.
WebUI (Element): https://riot.privex.io
We operate a public Mastodon fediverse server called Privex Social, which has lax rules/moderation, and privacy (protect your DMs from snooping / law enforcement / third parties) - as the server is hosted on our own hardware and network, and your data is legally protected through our Offshore Belizean company.
Sign up / Login here: https://privex.social
DNS is the protocol used to find out which IP address(es) and other records that a given domain such as
privex.io points to.
We operate several public DNS (Domain Nameserver) servers across our regions, which are available over both IPv4 and IPv6, and some are even available using DNS-over-HTTPS (DoH) so that your DNS requests are encrypted.
|Sweden (SE)||184.108.40.206||2a07:e00::333|| |
|Netherlands (NL)||220.127.116.11||2a07:e03::333|| |
|Germany (DE)||18.104.22.168||2a01:4f8:150:74d5::333|| |
|Auto-select Region|| ||Mainly for DNS-over-HTTPS - returns the geographically closest DNS server's IPv4/IPv6 address|
|Load Balance All Regions|| ||(NOT RECOMMENDED TO USE) Mainly for quickly looking up all of our current public DNS servers - returns ALL DNS server's IPv4/IPv6 addresses as multiple A and AAAA records. Due to the fact this returns multiple servers and the way SSL is retrieved, we don't recommend using this as your primary DoH server, we can't guarantee you won't occasionally run into SSL issues.|
DO NOT USE THESE DNS SERVERS UNLESS YOU HAVE AN IPv6-ONLY SERVER IN A REGION WITH NAT64 SUPPORT
A DNS64 server is a special DNS server which returns IPv6 AAAA records for IPv4-only domains, the IPv6 addresses which are returned are actually the IPv4 address wrapped inside of an IPv6 prefix, usually within the standard NAT64 prefix
64:ff9b::/96 - for example
Providers who provide IPv6-only servers / networks tend to setup a NAT64 gateway, with the prefix
64:ff9b::/96 (or another prefix if they expect you to use their DNS64 servers) routed at the network level to their NAT64 server, which converts your IPv6 traffic into IPv4 to the decoded address, as well as converting the returned IPv4 traffic back to your IPv6 source system.
Our DNS64 servers are generally pre-configured on our IPv6-only servers, so you shouldn't need to manually add these to your IPv6-only server from us, unless you've changed your DNS settings previously, or something went wrong with your server's network provisioning.
|Sweden DNS64 (SE)||2a07:e00::364|| |
|Netherlands DNS64 (NL)||2a07:e03::333|| |
|Germany DNS64 (DE)||2a01:4f8:150:74d5::333|| |
|Auto-select Region DNS64|| ||Mainly for DNS-over-HTTPS - returns the geographically closest DNS server's IPv4/IPv6 address|
|Load Balance All DNS64 Regions|| ||(NOT RECOMMENDED TO USE) Mainly for quickly looking up all of our current public DNS64 servers - returns ALL DNS64 server's IPv6 addresses as multiple AAAA records. Due to the fact this returns multiple servers and the way SSL is retrieved, we don't recommend using this as your primary DoH server, we can't guarantee you won't occasionally run into SSL issues.|
NTP is "Network Time Protocol", a protocol which is used for synchronising your system's date/time over the internet, to deal with the fact that most computer clocks drift by a few seconds/minutes over a few days/months.
We operate NTP (Network Time Protocol) servers in most/all of our regions using Chrony, to help keep your server's time as accurate as possible by having NTP servers on the same network as your server.
You can use them both within our regions, at home, or even at other server hosts - with both the classic
ntpd and the more modern
chrony (and possibly
systemd-timesyncd too) - simply set the NTP Pool config option to
chrony.privex.cc, or the NTP Server if your NTP software doesn't support pools (e.g. the built-in Windows / Mac "time server" field).
If you can only pick one server, please check our dedicated Time Servers article article for a list of our individual regional NTP servers, so that you can pick the closest NTP server to you.
|Hostname||Time Server Software||Location||IPv4||IPv6|
|de2.chrony.privex.cc (de2.ntp.privex.cc)||NTPD||Falkenstein, Germany||YES||YES|
For more information, see our Time Servers article
We operate several Privacy Frontends/Wrappers in collaboration with PrivacyTools.io, which are effectively proxies which can strip various tracking scripts, hide your IP address, or even provide a completely different frontend for the service. You can find more information about them HERE.
|Service||Clearnet URL||Tor Hidden Service|
IPERF Speedtest Servers
v4 only GeoDNS:
v6 only GeoDNS:
nl1.iperf.privex.cc (warning: UDP mode does not work over IPv6 on this server. UDP tests only work over IPv4 for NL)
example speedtest command against our NL speedtest server, over IPv6 and IPv4, in TCP mode, connecting to port 5206, with a target speed of 1G:
iperf3 -6 -b 1G -c nl1.iperf.privex.cc -p 5206
iperf3 -4 -b 1G -c nl1.iperf.privex.cc -p 5206
We run several Tor relays and exit nodes to help support the Tor network, since Tor is a public and free network designed to help you stay private and anonymous on the internet, it's only right that we as a privacy company try our best to contribute to the Tor network :)
|Name||Location||Relay Type||Network Speed||Notes|
|privexse1exit||Sweden (SE)||Exit Node||250mbps + 500mbps burst|
|privexnl1exit||Netherlands (NL)||Exit Node||500mbps + 1000mbps (1gbps) burst|
|privexrelayfin1||Finland (FI)||Relay||400mbps + 700mbps burst|
|privexrelayde1||Germany (DE)||Relay||800mbps + 1000mbps (1gbps) burst|
|privexrelayde2||Germany (DE)||Relay||800mbps + 1000mbps (1gbps) burst|
You can find a detailed list of our relays and exits here on yui.cat