A "vHost" (virtual host) allows users to hide their hostmask (i.e.,
xertion-6mau9k.fl.comcast.net) with something creative (i.e.,
i.am.the.doctor). The nickname must be registered in order to request a vHost.
- must contain a dot (aka
.) and can only contain alphanumeric characters, dots (
.) and dashes (
- must not contain a
- must not be an IP or IP look-a-like;
- must not resolve (basically, the vHost can't point to an actual site);
- Exception to this rule is if you own the domain. Please join #help and speak with an operator;
- must not contain colour codes. Colored vHosts are given at operator discretion;
- must not mimic government organizations such as FBI, CIA, ATF, Interpol, MPAA, or RIAA;
- must not contain the words 'ircop', 'admin', 'network', 'xertion', or any IRC Operator's nick;
- must not contain racist words (what is considered racist/derogatory by operator discretion);
- must not refer to other networks/spamming;
- must not refer to fraudulent activity. (dosing, rooting, "carding," etc.)
Project cloaks are vHosts assigned to your group, such as
wikia/acwiki/username. These types of vHosts cannot be requested using the HostServ system.
Project cloaks must be given by an IRC operator directly. Join #help to have these assigned to you.
- vHosts are regulated by a bot, which validates the vHosts against the rules. If your vHost keeps getting rejected and you think it is a mistake,
/join #helpfor further assistance.
- vHosts must then be manually approved.
- Ban evasion using vHosts will cause you to get: your vHost removed, network banned from Xertion for a set period of time, and vHost banned for an extended period.
Requesting a vHost
You must have a registered nickname in order to request a vHost. In order to register your nickname, please visit Register your nickname
To request a vHost, use the command
/msg HostServ REQUEST vhost.goes.here
Your vHost is activated automatically upon approval.
If it is not, you can turn it on using:
/msg HostServ ON
Understanding of the vHost system
When you request a vHost, it is sent to the staff for activation.
- So if you keep on sending your request without correcting your error, we see it. Over and over.
- This can take anywhere from 6 seconds, and a few hours.
- Not everyone on the staff lives in your timezone.
- Sometimes a staff member may defer an answer pending consultation with other operators.
- Reminding staff to approve your vHost is nothing but frustrating. The staff saw your request in every condition where you got a valid response from the vHost request system. Please wait patiently.
Please do not experiment with different vHost requests, or put in a default example and expect to change it a few minutes later.