Letzte Verbindung
Die folgenden Informationen wurden von unserem IRC-Crawler
während seiner letzten Verbindung zum Server
irc.sekurnet.org am 2026-10-22 um 18:12 Uhr (UTC) gesammelt.
Server Options
NETWORK=SekurNet CHANTYPES=# CHANMODES=beI,k,lfjL,imnprstzCNPQSTVROMcDuG PREFIX=(qaohv)~&@%+ NICKLEN=30 CHANNELLEN=50 TOPICLEN=307 CASEMAPPING=ascii MODES=6 STATUSMSG=~&@%+ AWAYLEN=390 KICKLEN=300 :
MAXLIST=b:
LINELEN=512 TARGMAX=PRIVMSG:
|
Admin Info
| Administrative info about irc.SekurNet.org
SekurNet IRC Network
irc.SekurNet.org - Europe
support[at]sekurnet.org
|
Message Of The Day (MOTD)
-
- ____ _ _ _ _
- / ___| ___ | | __ _ _ _ __ | \ | | ___ | |_
- \___ \ / _ \ | |/ /| | | || '__|| \| | / _ \ | __|
- ___) || __/ | < | |_| || | | |\ || __/ | |_
- |____/ \___| |_|\_\ \__,_||_| |_| \_| \___| \__|
-
- irc.SekurNet.org
-
- small network - secure by default - no nonsense
- powered by SekurIRCd v1.3.0
- https://gcanosa.github.io/SekurIRCd/
-
- =====================================================================
- NETWORK
- =====================================================================
-
- Plaintext ..... port 6667
- TLS/SSL ....... port 6697 (recommended - gets you user mode +z)
- Hostnames ..... cloaked; your real IP is not shown to other users
- Services ...... ChanServ /msg ChanServ HELP
- Accounts ...... /msg NickServ REGISTER <pass> (see ACCOUNTS)
-
- =====================================================================
- CHANNELS
- =====================================================================
-
- #SekurNet ........ main lobby - say hi
- #help ............ questions about the network or your client
- #gh-monitoring ... GitHub commit/update feed for our projects
-
- Want your own channel? See [ REGISTERING A CHANNEL ] below.
-
- =====================================================================
- RULES
- =====================================================================
-
- By connecting you agree to the following. No exceptions.
-
- 1. Be civil. No harassment, hate speech, threats or doxxing.
- 2. No flooding, spamming, advertising or mass-highlighting.
- 3. No botnets, drones, clones or connection proxies for abuse.
- Bots are fine if they behave and a channel op allows them.
- 4. No warez, cracks, malware, stolen data or illegal content.
- 5. No porn or NSFW content outside channels set up for it.
- 6. No nick or channel squatting, and no impersonating staff.
- 7. Channel ops run their channels; network staff run the network.
- Take disputes to #help, not to the channel you got kicked from.
- 8. Don't ask for oper. If we need you, we'll ask you.
-
- Breaking the rules gets you a kick, a K-line or a permanent ban -
- our call, no appeals via PM spam. Incidents may be reported to
- your provider. If you wouldn't let your kids do it at home, don't
- do it here.
-
- =====================================================================
- ACCOUNTS: REGISTER A NICK
- =====================================================================
-
- Register once, then log in each time you connect:
-
- 1. Register: /msg NickServ REGISTER <password>
- or /REGISTER <account> <password>
- You are logged in at once; the account is named after your nick.
- 2. Log in: /msg NickServ IDENTIFY <password>
- other name /msg NickServ IDENTIFY <account> <pass>
-
- Best way: SASL. Put your account and password in your client's
- SASL PLAIN settings and it logs you in while connecting - no
- IDENTIFY needed. Clients with IRCv3 account registration
- (draft/account-registration) can create the account for you.
- TLS users can log in by certificate instead: /CERT ADD
-
- Pick a strong password and keep it to yourself.
-
- =====================================================================
- REGISTERING A CHANNEL
- =====================================================================
-
- 1. Create it and hold op: /JOIN #mychannel
- 2. Register it: /msg ChanServ REGISTER #mychannel <pass>
- 3. Keep it alive (optional) /msg ChanServ JOIN #mychannel <pass>
- ChanServ stays inside, so the channel survives everyone leaving.
-
- Lost op after a reconnect? Get it back with:
-
- /msg ChanServ IDENTIFY #mychannel <pass>
-
- Share ops without sharing the password:
- /msg ChanServ ACCESS #mychannel ADD *!*[at]their.host o <pass>
-
- Pick a strong channel password and keep it to yourself.
- Full command list: /msg ChanServ HELP
-
- =====================================================================
- SECURITY: SCANNED FOR YOUR PROTECTION
- =====================================================================
-
- To keep drones, botnets and open proxies out, every connection is
- checked automatically by our Protection bundle:
-
- 1. DNS blocklists - your IP is looked up in DNSBLs of known
- open proxies, drones and abusive hosts.
- 2. Proxy scan - your IP may be scanned: the server opens a few
- connections back to your address on common proxy ports (HTTP,
- SOCKS4, SOCKS5) to test whether it relays traffic. It never
- reads your files or data - it only checks for an open proxy.
-
- Seeing short connections from us in your firewall log right after
- you connect? That is why - nothing is wrong, no action is needed.
-
- Listed, or found to be an open proxy? The address is banned for a
- while. Close the proxy, then ask in #help and we will sort it out.
-
- =====================================================================
- PRIVACY
- =====================================================================
-
- Server logs are kept for abuse handling only and are never sold
- or shared. Staff never ask for your password - don't give it out.
-
- =====================================================================
-
- Type /MOTD to read this again. Be smart. Be chill. Have fun.
-
|