SERVICE LEVEL AGREEMENT.
Racknet /We refers to Racknet.in
You/Customer/Client refers to any individual/company using Racknet’s services
By using or continuing to use Racknet’sservices, you are automatically agreeing to the terms of this document.
Domain Registration : Racknet may take at least three to seven business days factoring in on elements like holidays, internal processing issues etc. and in all such cases, the Company cannot and shall not be held liable if your domain name gets registered by some other party. In case of any dispute arising out of this, the company’s liability shall be restricted purely to making refund of the amount received by it for a new domain request and not beyond.
Domain Renewals : : You (client) acknowledge that it’s your responsibility to keep records and maintain reminders regarding the expiry of any service. As a convenience to the client, and not as a binding commitment, we may notify you of any expiring services, via an email message sent to the contact information associated with the Customer in the Racknet’s database. Should renewal fees go unpaid for an service, the service will expire automatically & Racknet will not be responsible for any loss that may occur due to expiry/termination of services.
Domain Transfer : : Due to the unpredictable nature of the transfer process, no guarantees is made regarding the amount of time a specific transfer may take. If the transfer of the domain is done by Racknet.com on behalf of the account holder a handling fee may be incurred. If the customer cancels service during the transfer period for any reason, all charges are considered earned.
Domain Registration/Renewals/Transfers is governed by ICANN Policy.
SHARED HOSTING USAGE POLICY.
Any action/processes that abuse/harm Racknet’s server or negatively impact other clients’ service experience is strictly prohibitied.
Processes invoked by the web server, cron, shell or any other method should not exceed the following limitations :
Consume more than 256 MB of RAM.
Utilize in excess of 15 seconds of CPU time.
Number of open files should not exceed 64.
Create core dumps.
Number of simultaneous processes should not exceed 5.
Execute a script/binary that forks in a way to create a fork bomb.
Programs may not run in the background or listen on a network port. If you require a bot, service or daemon, you should consider a dedicated server, as very few shared web hosts allow this type of program.
All users are restricted to 15 concurrent MySQL/MSSQL connections.
Database servers should not be used as a hosted solution. Database access should only be used for the web site hosted by Racknet.
Remote database access is for administrative purposes only.
Any particular database that abuse/harm Racknet’s servers or negatively impact other clients’ service experience is strictly prohibitied. Racknet’s own the rights to suspend or terminate any database that abuse/harm Racknet’s servers.
Files and Directories
The total number of inodes in an account may not exceed 75,000. Every file (a webpage, image, email, php file, directory, etc.) on your account uses up one (1) inode. This is not something we actively enforce and it will only become an issue if a client is causing problems for other people on the server. We will of course notify you if this is the case with a full explanation.
A directory cannot contain more than 2,500 immediate child files. This includes subdirectories themselves, but does not include files contained within those directories.
Simultaneous IIS/Apache connections may not exceed 50 from one individual source at any given time.
Web processes should not fork or spawn subprocesses.
The number of hits on website hosted on shared server can’t exceed to more than 50,000 hits/day.
Email and Mailing Lists
Email ID size should be 500 MB each . Though you can create unlimited Email IDs.
Files in excess of 10 MB should not be sent via email.
Processes should not send outbound mail to more than 25 recipients at any given time.25 Emails/5min.
SMTP connections (outbound email connections) are limited to 500 per hour per server account.
Mailing lists larger than 1,500 will require a semi dedicated, VPS, or dedicated server from us. Dividing one list into smaller parts to get around this limit is not allowed.
Any mailing list over 900 emails is only allowed in off peak times such as Saturday and Sunday or from 1am to 8am ET during the week.
Any mailing list must be throttled so that it sends an email every 6 seconds at the very minimum. If the mailing list software you are using doesn’t support throttling you must use something else. We do this as this keeps the server load from going very high and causing problems for other users. If you don’t do this you will be suspended.
We do not allow you to send to a mailing list you were given or that you bought. This is spamming and we have zero tolerance for this.
No Direct SMTP mailing system scripts are permitted. Mail should be relayed through the local MTA.