Radio en Línea ·
From a volunteer community to an independent association
Libera.Chat announced its launch on May 19, 2021. Its announcement explains that much of the team came from freenode and sought to continue a collaborative platform for free software and related projects under an independent structure.
Its legal home is a Swedish nonprofit association, registration number 802535-6448. Volunteer staff members hold equal voting power. A single “owner” is therefore an inaccurate description: the association and its elected bodies govern the network.
The official page checked lists moonmoon as chair and Swant as treasurer. Engineering, Operations, and Projects and Community have separate responsibilities. Membership can change; check current roles before attributing a decision to an individual.
Servers and ports published by the network
The recommended general endpoint is irc.libera.chat with TLS on port 6697. This hostname lets the network manage server selection; fixing an IP or internal server can prevent your connection from following infrastructure changes.
Enable TLS in your client or ZNC network settings and verify the certificate. For hostname or trust errors, check the endpoint and system trust store instead of disabling verification.
- TLS: 6697, 7000 and 7070.
- Plaintext: 6665–6667 and 8000–8002; these are not encrypted connections.
- Regional endpoints: irc.eu.libera.chat, irc.us.libera.chat, irc.au.libera.chat and irc.ea.libera.chat.
- IPv4 only: irc.ipv4.libera.chat. IPv6 only: irc.ipv6.libera.chat.
Your network account, nickname and ZNC account
Your visible nickname and registered account serve different roles. For automatic identity verification, use a mechanism documented by Libera.Chat, such as SASL or CertFP, with your own credentials. Your ZNC provider login does not replace your network account.
ZNC creates two links: your device connects to the bouncer and the bouncer connects to Libera.Chat. Configure TLS for each link. Encrypting only the connection from your phone does not automatically encrypt the bouncer’s network connection.
For a bot, provide the bot nick, channel and your authorized identity separately. Adopting another person’s nickname does not prove ownership and must not grant owner privileges.
What to check before bringing a community or bot
Libera.Chat focuses on free software and collaborative projects. It publishes naming, project-registration and channel policies; reserving a channel name does not establish recognized project status. Choose the appropriate procedure for your community.
Read network and channel rules before automating announcements, bridges or games. A bot needs an agreed purpose, restrained message volume and permission from channel administrators. An external commercial service cannot guarantee exemptions from Libera.Chat’s rules.
For network assistance, use its documentation and staff-designated help channels. For bouncer or bot-script issues, contact that provider. This distinction routes each incident to whoever manages the affected component.
Sources and verification date
Information checked on 2026-10-13. Ports, operators and policies can change; check the sources before setting up a connection.