GigeNET

Which Email Protocol do I choose? IMAP or POP3?

Email is, by far, the most common means of online communication these days. Believe it or not, email dates back nearly 50 years and has seen little change in that time. An email sent in the early 1970s would look much as it would today. The key to email’s success is that it is based on a series of well-defined standards with a decentralized design that will likely help email remain in wide-spread use for a very long time.

Email operates using a classic client-server model. A client is a program that end-users (you) interact with. Common email clients are Outlook, Thunderbird, various email clients built into operating systems (like Microsoft Mail and Apple Mail), and web-based email clients (Hotmail, Gmail, to name a couple). This is where incoming messages are read and outgoing messages are composed.

The server is another program that makes the whole system work behind the scenes (at least from the end-user point of view). Email clients connect to the server regularly to check for new messages and to dispatch outgoing emails. Each email server connects to the global network of email servers in order to route mail all over the world, making sure each message is delivered to the correct server, and eventually to the recipient when their client connects to their own server.

Configuring Your Email Client

Inbound and outbound email messages are handled by different protocols, and often – especially with larger email systems – by separate servers. Configuration of the client requires you to know the hostname and port used for both inbound (new mail) and outbound (sent) messages. This information is often found on the mail server’s interface, if you are managing your own email server. Otherwise, it can be requested from the server’s administrator. 

Outbound (sent) messages are handled almost universally by SMTP, so we’ll address that first.

SMTP (Simple Mail Transport Protocol)

Outgoing email configuration is usually as simple as specifying the SMTP server, network port, and supplying credentials for authentication. The SMTP server is the device your email client connects to in order to relay messages sent by you to the email server corresponding to the recipient’s email account. It is typically something like smtp.domain.com or mail.domain.com.

A network port is a thread of a network connection. If you transmit data on port xyz, it will come out port xyz on the other end. SMTP historically uses port 25, but modern systems tend towards port 587 these days. Occasionally you will see 465 (deprecated), 2525 (non-standard), or less commonly a unique port number.

Finally, you will need to authenticate with your SMTP server to prove that you are authorized to send email through this email relay server. This will be the same username and password you use to log into your email account.

Configuring a client for incoming email is a bit more complex because there are two commonly-used methods to choose between. Some email servers may only support one method, so your decision has already been made for you.

POP3 (Post Office Protocol)

POP3 is a protocol that mail clients use to download email messages from an email server and store them on the local machine. This is the original protocol that is used to fetch email from a mail server and the most widely available. When using POP3 your mail client will contact the mail server to check for new messages. If any are found, they are downloaded to the email client and deleted from the server (there is often a setting to delay this deletion). 

POP3 was at its prime during the age of dial-up and transmits a minimal amount of data between client and server. It also keeps the space used by your email account low since messages are only stored on the server until they are downloaded by the client. While these were both big selling points when dial-up was the norm, they are pretty much inconsequential now unless you are dealing with a poor or spotty internet connection.

POP3 can be problematic when using multiple clients to access the same email account. Since messages are deleted after delivery, by default, they only appear on the client that downloaded them. This can lead to some messages on your phone client, and others on your desktop client, though this can be mitigated somewhat by delaying the deletion on the server. Additionally, POP3 clients lose all messages if the data on your client device is lost or destroyed with no way to recover them if you don’t have a backup.

Configure POP3 on your client by entering the server name, network port, and authentication. POP3 typically uses port 110 for unencrypted connections, and port 995 when encryption is used.

IMAP (Internet Message Access Protocol)

IMAP differs from POP3 in that it leaves email on the server. When a client connects to check for new mail, the latest messages are synchronized with the server, downloading copies of new messages. IMAP clients often cache a number of messages on the client for off-line access, but local storage use is minimal. This fits well with the always-online reality of today, and doesn’t bog down mobile devices with large email archives, where storage can be at a premium. You can access your mail from any number of IMAP clients and see the same messages, and losing a device or upgrading to a new one doesn’t cost you your email history. 

In most ways, IMAP is superior to POP3, but it may suffer when your internet connection is spotty or you want to have access to your entire email account off-line.

Configuration of a client for IMAP uses the typical server name, network port, and authentication we’ve seen before. In this case, the standard ports are 143 for a standard connection, and 993 for an encrypted one.

Which do I choose? IMAP or POP3?

POP3 is an old protocol and it has had its time and place. As a result, IMAP was designed to address the shortcomings of POP3 and keep up with how email is used in this modern day and age. Given a choice, go with IMAP. There are a few situations where POP3 may be prefered, and in some cases is the only option available. Should you find yourself having to use POP3, do yourself a favor and set it to put off email deletion on the server for as long as possible (indefinitely, if you can).

Hopefully, this guide has helped you better understand how email works – which is a good thing, because it will likely be around for a long time. I find it interesting to see how the protocols that facilitate client-server communication have evolved to keep up with the times, yet the appearance of an email message has remained essentially unchanged.

A few key practices that can secure your server

The advent of the Internet Age has had a profound effect on how business is conducted. Maintaining an online presence is no longer optional for most companies if they want to stay relevant and competitive. Existing and potential customers use the Internet to make purchases, manage their accounts, research products, and much more. The benefits of this are immeasurable, but it doesn’t come without a dark side — hackers. With so much riding on your website and online reputation, it is absolutely vital to keep your servers secure. 

Security professionals devote their entire careers to keeping up with the ever-evolving nature of online threats and global corporations have whole teams with substantial resources dedicated to keeping their online properties secure. Taking on the chore of securing your server may seem like a daunting task, but we’re here to help! We have identified a few key practices that can secure your server enough to defend against the vast majority of attacks and dissuade all but the most elite hackers. It doesn’t take a large amount of system administration ability to secure your server using these methods, but look into our management plans and SecureServer+ services if you’d rather leave it in our capable hands. 

Get Behind a Firewall

The first line of defense for any secure environment is a firewall. There are several firewalls to choose from, but they all typically have the same basic features. A firewall is either an application or a physical device that resides between the internet and any network-facing services on a server. It acts as a gatekeeper for network traffic, using a set of rules to filter both inbound and outbound connections. However, a firewall is only as good as the rules it is given to work with. A well-configured firewall can filter out the vast majority of malicious connections, while a poorly-configured one will be far less effective.

The first decision is hardware or software. Most modern operating systems come with a built-in software firewall application, which is usually sufficient. A dedicated appliance, also known as a hardware firewall, is often used in front of multi-server environments to provide a single point for firewall administration.

No matter what type of firewall you end up using, your next step is defining a good set of rules. Rule number 1 when configuring a firewall, especially remotely, is to be very careful to not lock yourself out by blocking the connection you are using to access the firewall. It is always good practice to have a fallback access method to change firewall rules should you accidentally block your own connection – typically a physical console or an out-of-band console solution like IPMI, ILO, or DRAC.

Start by considering what services your server provides. Network services utilize specific ports to help differentiate between types of connections. Think of them as lanes on a VERY wide highway with dividers to prevent one from changing lanes. A webserver, for example, will typically use port 80 for standard connections and port 443 for connections secured using an SSL certificate. These services can be configured to use non-standard ports so be sure to verify which ports your services are using.

Next, determine how you will remotely administer your server. On Windows, this is typically done via RDP (Remote Desktop Protocol) and on Linux, you will likely be using SSH (Secure Shell). Ideally, you will want to block access to the ports used for administration to all but a handful of IPs or to a small subnet in order to limit the access to these protocols from anyone not within your organization. For example, if you are the sole administrator of a Linux server, open the SSH port (typically 22) to connections from only your computer’s static IP address. If you don’t have a static IP address, you can often determine a subnet from which you will be assigned an IP. While whitelisting a range of IPs isn’t ideal, it’s far better than opening up that port to the whole Internet. 

To generate a solid set of rules, block all ports from all IPs then create specific rules to open those ports needed for your services and administration – remembering not to lock yourself out. The ports opened for your services should generally be open from all IPs, but limit administration ports as discussed above.

While a firewall shouldn’t be your only line of defense, creating a reasonable set of firewall rules is a great starting point for enhancing your server’s security. In truth, no server should be without at least a basic firewall configuration.

Authentication & Passwords

One of the simplest ways to enhance your server’s security is simply by enforcing a strong authentication policy. Your server is only as secure as the account with the weakest password. Follow good password guidelines for any password used on a server, such as making sure that your password is of adequate length, not a dictionary word, and not used on other services that could themselves become compromised and leak your password. While you can limit remote access to your server via a good firewall configuration, there are still exploits that can be used to send commands to a system through compromised or unpatched services running on open network ports.

In many cases, it’s possible (and more convenient) to go passwordless altogether! If your main method for accessing a server is via SSH, you can disable password authentication in your server’s SSH config file and instead use a pair of public and private keys to authorize your connection.

Keep in mind that this method may not be as convenient if you need to be able to login to your server from anywhere at a moment’s notice, since you will need to add your private key to any new system you are connecting from. Also, while this approach makes remote connections an order of magnitude more secure, don’t neglect to never-the-less set a strong password on your account. Hackers are sometimes able to access a system in other ways, and you wouldn’t want to have an account with elevated access secured by a password like, “1234.”

These days, two-factor authentication (2FA) is becoming very popular. When using 2FA, not only does a user need to authenticate with their password, they also need to provide a one-time-use code sent to a previously registered email address or mobile device to further verify their identity. Implementing something like this on your server could be done through a third party service, or by using a 2FA-enabled account (like Google or Microsoft). cPanel\WHM now supports two-factor authentication, so this may be an option for you if you use this control panel as your main means of server administration.

Brute Force Protection

A common attack vector on servers is a brute force attack. These are remote login attempts using guessed usernames and passwords, repeated over and over, as fast as the servers and network will allow. Unprotected, this can be several hundred thousand attempts per day — enough to crack any 8-character password in a month. For this reason, it is prudent to install some form of brute force protection on your server.

Most approaches to brute force protection take one of two forms. The first method introduces a timeout between login attempts. Even if this timeout is as short as a single second, this can cause an attack to take many times longer to crack the password. You’d likely want a longer timeout to provide better security, while not overly-interfering with legitimate login attempts by users making typos. Some systems take a clever approach to this method by increasing the timeout with every failed attempt, often exponentially. Fail once, wait 1 second. Fail again, wait 5 seconds. Fail a third time, wait 30 seconds… By the fourth attempt, you’re going to be very careful entering your password.

Alternatively, a variation of this method puts a hard cap on the number of attempts allowed within a set period of time. Failing to login too many times will get the account locked out – either temporarily, or in more extreme cases, until unlocked by a server administrator. This method effectively puts a stop to any brute force attacks, but it can be more annoying for valid users who aren’t very careful about entering their passwords.

The second method is to introduce a Captcha to the login request. This forces the user to perform a feat that is trivial for a human, but difficult for a computer. Often, this involves some sort of image recognition, such as identifying all the pictures in a grid that contain a street light, or deciphering some text written in a blurry font. While computers are usually able to solve these requests eventually, it takes them much longer than a typical human and greatly slows down the attack. Captchas are also often used to protect public comment sections from spam posts and sign-up forms from fake account creation.

Brute force protection can be found in many firewalls, or in the operating systems themselves — but don’t forget about other accounts, such as WordPress, cPanel/WHM, etc. Make sure any exposed login has some form of brute force protection enabled.

Software Updates & Security Patches

Software and operating system updates and security patches are also important to maintaining a secure server. All of your other efforts can mean nothing and go entirely to waste if you are running an outdated version of an operating system vulnerable to known exploits.

Most software and operating system vendors dedicate significant resources into keeping their products patched against the most recently discovered exploits, so much so that many minor releases contain more security fixes than feature updates. Maintaining this level of vigilance on older versions of their products can be costly, so software and operating systems are frequently classified as End of Life (EOL) after a number of years. Among other things, this means that the product will no longer receive updates for exploits that may be discovered after EOL has been reached.

A commonly seen case of this type relates to PHP, a scripting language commonly used on the web. At the time of this posting, all PHP versions older than 7.2 are EOL. Despite this, PHP versions as old as 5.3 are still common out in the wild. There are significant differences between 7.2 and 5.3, making upgrading to a supported version impossible without significant reworking of the code. 

Fortunately, with this specific example of PHP versions, CloudLinux has you covered on a cPanel server. CloudLinux offers hardened versions of old PHP versions, as well as security updates, well past the EOL date. However this issue could happen with any software, and most don’t have a solution as simple as CloudLinux. 

It is not good practice to run outdated operating systems either. For example, CentOS 5 has been EOL for some time, yet it is not a terribly rare sight. If you happen to be running something like this, you should be planning your upgrade path as soon as possible. When the operating system you are running on goes EOL, it’s common that even supported software on your server will also stop receiving updates, since vendors won’t qualify new versions on EOL OS versions. This can have a cascading negative effect on the security of your server.

Code & Custom Applications

Unfortunately, even the most hardened server can still be vulnerable to attacks through insecure code or applications running on a website.

If you are running a customizable web application, such as WordPress, Joomla, or Magento, it is critically important for you to keep not just the core application up to date, but any plugins or themes as well. This also applies to the code of the project themselves – if you suspect that your theme or plugin is “dead” and no longer being updated, it is prudent to look for alternatives. New exploits are constantly being discovered, and an application or plugin is only as secure as it’s last update.

When dealing with custom code created for you by a developer, it is wise to maintain a continued relationship with your developer so that you can continue to receive updates. Otherwise, you may end up in a situation as described above, where you find that you can no longer update your PHP or other important software because the website is not compatible with the new version.

This attack vector can be the hardest to defend against, because your datacenter or hosting provider generally can not support the custom software and code that is running on your server. Unless you are running entirely off-the-shelf software, make sure you have a plan to keep your code updated and patched.

As you can see, securing a server goes far beyond the initial setup. While this is important, equally vital is keeping it up-to-date in order to combat the ever growing list of known hacks and exploits. The damage caused by a compromised system, both financially and to your reputation, can be massive. As the old adage goes, an ounce of prevention is worth a pound of cure. 

For much of the Internet’s history, online multiplayer gaming has been a cherished pastime for many. The first multiplayer game is believed to have been played as early as 1978 – less than a decade after the birth of ARPANET. Technology has come a long way since then, but suffering from lag and latency has remained a constant struggle for gamers everywhere. While modern networks are far more efficient than our dialup modems of decades past, games have evolved as well, requiring vastly larger amounts of data to be transmitted between participants. Continue reading…

Despite being one of the foundational pillars of the Internet, DNS is often a poorly understood service, even by otherwise tech-savvy people. We often find DNS nameserver setup to be a frequent source of confusion for new clients migrating to our servers. 

Due to the nature of shared hosting, DNS services are typically managed by the hosting provider. However, when upgrading to a dedicated server or to a cloud server, that responsibility will typically fall on you. Hopefully, we can help shed some light on DNS to improve your understanding of this important component of your environment. Continue reading…

Did you know that GigeNET has the highest customer retention rates in the industry? So it comes as no surprise that many of our customers have been with us since day one. One such customer is Royal Wholesale, an online wholesale distributor of high-quality bulk candy, wholesale chocolate, confectionery products, and snacks. Royal is going into their 30th year of business and has known from the very beginning the importance of choosing a reputable hosting company to meet their needs. 

With over 4,000 products on their eCommerce website, it’s crucial that Royal has a dedicated hosting company that can keep their website running smoothly and efficiently. With a dedicated server from GigeNET, Royal’s website is hosted on a server that is entirely dedicated to their business on the fastest-route optimized network.

To avoid downtime and lost revenue, Royal has chosen remote backups from GigeNET as a means of providing data security and to help maintain stable operations. With thousands of products and customers, having a strong backup strategy in place is paramount to ensure data retention and restoration. 

Royal has also secured the connection between their website and its visitors by encrypting the traffic with an SSL (Secure Socket Layer) certificate. They value their customer’s personal information and wanted to do everything they can to ensure that it remains private. Adding an SSL certificate to your website like Royal has, will give your customers peace of mind that they’re visiting a safe and secure website run by a brand they can trust.

Although Royal Wholesale the most technologically advanced wholesale distributor in the confectionery industry, they need to focus on running their business, not their dedicated servers. For this reason, Royal chose to take advantage of GigeNET’s fully managed dedicated server hosting. With this level of hosting, Royal receives IT infrastructure support from GigeNET’s engineering team, world-class data centers, an industry-leading network, hardware, infrastructure, and support Service Level Agreements. If you’re interested in learning more about how GigeNET’s products and services can help your business like we’ve helped Royal Wholesale, contact us today.

In today’s security-focused world, securing your website, as well as the server it is running on, is an important and necessary task for any website owner. SSL certificates are on the front line of this defense, serving to secure the connection between your web server and your clients. However, it can be an intimidating concept for beginners, given all the various options and different levels to choose from — so how do you know what your website needs? Should you buy the most expensive certificate available, or settle for a free SSL certificate?

What is SSL, anyway?

The primary function of SSL (Secure Socket Layer) is to secure the connection between your website and its visitors by encrypting the traffic while it’s in transit over the Internet. This provides numerous benefits, including combating man-in-the-middle attacks. The idea behind encryption is even if someone along the way can view the data while it’s in transit, they need the encryption keys to decipher it into something readable.

In addition, an SSL certificate serves to validate the identity of a website. For example, if you go to your bank’s website you want to know that the website is indeed operated by your bank, and not by an imposter. This helps to protect against phishing attempts and other fraudulent behavior that can damage your brand, or worse.

Type of SSL Certificates – and what’s the difference?

There are several common types of SSL certificates which you’ll see when you’re shopping around.

The key difference between the SSL certificates is how they are verified, and how much of a vetting process is involved in checking the identity of the applicant. This is done by the issuer of the SSL certificate, known as the certificate authority. Often, the quality of a certificate is tied directly to the reputation of the issuing certificate authority.

Paid SSL certificates typically also come with an insurance policy, providing financial compensation if there is a breach in which the certificate authority could be found at fault. This is vital protection for a website operator who is handling monetary transactions, such as an eCommerce site. Usually, this insurance coverage will increase with a more expensive SSL certificate offering. You would want to check with your SSL vendor if this is important to you.

Domain Validated (DV) SSL

A domain validated SSL certificate is usually the cheapest and most common type of paid SSL certificate. While you do usually place company information into the certificate request, none of this is actually vetted when applying for the certificate.

The only thing checked is that you control ownership of the domain name covered by the SSL certificate. Usually, this is checked by one of a handful of common methods, such as creating a DNS TXT record, receiving a validation email on an administrative contact email address for the domain, or placing a validation code into the website’s code.

A DV SSL certificate from a common certificate authority will be accepted by any major web browser and will show a standard https:// link, sometimes with a green text or a padlock icon to indicate that the site is secure. It is the most common type of certificate and is an everyday sight while browsing the web.

Organization Validated (OV) SSL

An OV SSL certificate is similar to a DV SSL certificate, but additional details of the company registering the certificate will be vetted by the certificate authority. In addition to everything a DV SSL provides, the certificate authority will generally provide a secure site seal, which is an image which can be embedded within the website which visitors can click to get more information about the website owner. 

An OV SSL certificate otherwise will appear the same in a visitor’s web browser. The additional vetting is simply an option to provide added credibility to the visitor that the website is being operated by a legitimate business.

Extended Validation (EV) SSL
An EV SSL certificate is the most expensive type of SSL certificate and brings with it the most thorough vetting process. Before issuing an EV SSL certificate, the certificate authority will verify that the applicant company is an existing legal operating entity with a physical place of business, verify applicant details against official records, and independently verify that the applicant company has authorized the issuing of a certificate. Generally, this validation process is the slowest, as it often requires a verification letter to be sent through the mail.

The significant benefit of an EV SSL certificate is that it displays differently in the visitor’s web browser. In addition to displaying as a valid SSL-secured connection, in most web browsers an EV SSL will also display the name of the company in green text just before the URL in the address bar. This increases a visitor’s confidence in the legitimacy of the business operating the website.

What about the free SSL certificate options?

With the push to put SSL on every website, these days there are some certificate authorities offering free SSL certificate options. Some popular options include Let’s Encrypt and cPanel’s AutoSSL. With these options in play, is there a reason to pay for an SSL certificate anymore?

Many website owners can now benefit from the free SSL certificates that are available from such providers. Generally speaking, these SSL certificates are comparable to the lowest end paid certificates, Domain Validated (DV) SSL certificates.

From a security standpoint, generally, there isn’t a downside to using the free SSL certificates from these vendors. They provide comparable levels of encryption and show as valid and secure in any major web browser. One potential downside is that they may require more expertise to set up, though cPanel’s AutoSSL makes the setup pretty straightforward.

Keep in mind, if the insurance provided with paid SSL certificates is important to you, this is generally absent from the free SSL certificates. This reduces the accountability of the certificate authority and therefore may make these a poor fit for websites handling financial transactions or busy eCommerce sites.

Which SSL certificate is right for me?

As always, you should do all the necessary research to make sure all of your bases are covered, but a good rule of thumb might be:

• For a small, personal website, not handling financial transactions (such as an online resume or personal blog) a free SSL certificate or a DV SSL is usually sufficient.
• For a larger site, eCommerce, or any site handling financial transactions a paid DV SSL certificate would be the minimum. If you are concerned about appearing as a legitimate business or insuring your business in the event of a breach, you may want to consider the more expensive certificates such as OV or EV SSL due to the increased insurance coverage and the trust conveyed to visitors by these certificates.

Whichever option you choose, any level of SSL protection is better than none. GigeNET can help you find the right certificate for your business and navigate the process alongside you, from start to finish.

We are posting this notification to inform you that cPanel is changing their pricing structure, effective September 1, 2019. This change is not only an increase in price but also a change in how their license fees are calculated.

Beginning September 1, 2019, cPanel licenses will still charge a base fee for their licenses, with different pricing for physical and virtual servers. In addition, they are now charging based on usage. The base licenses will cover a set number of cPanel accounts and going over that number will incur a per-account charge.

We understand this is a significant price increase, especially to those with a large number of cPanel accounts. Our relationship with cPanel gives us access to discounted pricing, which will hopefully help to dull the impact of this change. We intend to forward our costs for these licenses to you with no markup by GigeNET, as we have always done. Most licenses do not exceed the base number of accounts, but those that do will incur an overage charge at the end of the month, but the exact method to bill for these overages is still to be determined.

A summary of the pricing changes can be found below.

 

# of Accounts	Current Price (Unlimited Accounts)	Up to 5	Up to 30	Up to 100	Over 100
Virtual Machine	$11.00	$12.50	$17.50	$32.00	+ $0.10 per Account
Physical Server	$25.00	N/A	N/A	$32.00	+ $0.10 per Account

Under the new pricing, a virtual machine license with 7 accounts would increase in price from $11.00 per month to $17.50 per month. This is because the account usage is more than 5, but less than 30.

The same usage on a physical server would change the price from $25.00 per month to $32.00 per month. This is because there are no pricing tiers with fewer than 100 accounts available to Physical Servers.

A physical server using 107 accounts would change from $25.00 per month to $32.70 per month. The base price of $32.00 covers the first 100 accounts, and the additional 7 accounts add $0.70.

We are still determining the logistics of billing for cPanel licenses under the new pricing structure but wanted to make sure we communicated this upcoming change as soon as possible. Please bear in mind that this change is originating with cPanel and that it is being extended to all of their license holders and resellers.

We will personally follow up with any clients that are about to exceed the base account limit. In addition, this change may force some to look into other options, and our team is ready to assist. Please reach out to your GigeNET account manager at (800) 561-2656 (option 1) if you have any questions or concerns.

Regards,

GigeNET Management

Whether you’re talking about the world of business or the world of computing, it’s a fact that changes come at you fast.  As those changes come at you, failing to adapt your computing infrastructure to new situations can mean you’ll be left behind.  But how do you know when it’s time to upgrade your web hosting plan?  At GigeNET, we know that making upgrades to your hosting plan is about more than just spending more money on a bigger plan.  We like to focus on providing targeted upgrades to the areas where our clients need them the most.  Here are a few common situations our clients have run into, and the solutions we can provide to solve these frequently encountered issues.

A Need for Speed

If your website is running slow, the problem may not be on the user end; it may actually be an issue with your server configuration.  For example, you may think that hosting your site on a server with an RPM hard drive is a good way to save money but when your customers run into long wait times when browsing, they’re likely to turn to your competitors.  Making the switch to a server with a Solid-State Drive (SSD) is just one way to help your site runs faster and that your customers get all the information they need without the frustration of slow loading times.

Security Concerns

As we get deeper and deeper into the 21^st century, hackers and other malicious actors have been able to keep pace with the rapidly advancing computing environment.  If you want to stay a step ahead of them, you may need to make some upgrades to your own computing infrastructure.  GigeNET has long been a pioneer in preventing DDoS attacks and other malicious intrusions so you know we’ve kept up with the techniques and tools used by hackers.  When you’re browsing our web hosting options, ask about our automated DDoS protection and other services to help you and your customers stay safe.

A Lack of Resources

In the same way that real-world resources are limited, system resources often need to be used by multiple applications and multiple machines.  When your resources aren’t keeping up with demand, it may be time to make some upgrades. GigeNET offers a wide variety of server options so you can easily upgrade resources like hard disk space, CPUs, RAM, and more.  Whether it’s a dedicated server or a virtual machine, we make it simple to add resources!

Managed Hosting Plans

At a certain point, managing your business’s web hosting in-house will become unwieldy and will take resources away from other crucial business functions.  Why not take those concerns off your hands and leave them to the experts at GigeNET?  We offer managed cloud hosting solutions so you can leave the hosting to us and focus on your customers.

No matter what your company’s computing needs may be, GigeNET has a solution!  Rather than offering tiered plans, we think it’s important to tailor every aspect of our services to the specific client.  When web hosting services are customized to meet your needs, you save time and money, so get in touch with us today by dialing (800) 561-2656 or by sending an email to sales@gigenet.com.  We’ll help you find the web hosting solution that works for you!