We understand first hand how unnecessarily complicated and difficult purchasing an SSL Certificate can be. That’s why we’ve revamped our entire SSL Certificate flow—everything from purchasing the certificate to verifying your information and installing it. So, why does this matter and who really needs an SSL Certificate?
Many years ago the World Wide Web made a promise. It told people that they could build their own website and it would look sleek and pretty. Many websites were made, but many people were disappointed. Many websites have been abandoned, fading away as low-price, low-quality promises on the lonely outskirts of the Internet.
Innovative shared hosting operating system (OS) developer CloudLinux and leading domain name registrar Name.com announced today the details of their growing partnership. Name.com is now using the CloudLinux OS, a switch that has had an immediate impact on load times, stability, and the overall customer experience of Name.com’s shared hosting services. The relationship began when Name.com identified potential issues with its existing environment.
“We take pride in our growing relationship with Name.com because the company is a lot like CloudLinux,” says Igor Seletskiy, Founder and CEO at CloudLinux. “Name.com is renowned for its customer support, giving webmasters the assistance they need to get the most from their hosting. However, when problems occur with an OS, maintaining support and service quality is difficult. At CloudLinux, we are very committed to our customers, and, in this case, we used our own excellent customer support team to help Name.com eliminate its issues.”
First, we enabled “two factor authentication” for an extra layer of security while signing in to your Name.com Account. We call it NameSafe.
Then we enabled Social Login as another option for logging in to your Name.com Account. Just check out the fancy Twitter and Facebook log in buttons.
AND now, we’ve outdone ourselves. We have created the most secure method possible for logging in to your account and protecting your domains. Let us introduce…..Name.com Facial Login!!! With Facial Recognition technology you can now log in to your Name.com account by scanning your face! It’s true!
Ashley Forker, Marketing Manager says, “We know your domains are your business and we’re here to help protect them. We’re always pushing the envelope on new methods to protect your account. I looked around the office during our annual holiday party and realized – hey – no two faces are alike. We should allow people to log in with their face!”
Bill Mushkin, Name.com Founder, eavesdropped and agreed. He immediately left the party and begun work on our patent PhotoPixel Technology. This breakthrough in biometrics paved the way for facial recognition technology. The result – Name.com Face Login. Bill’s been traveling the world since the new year testing our image recognition technology with all cultures.
Think you can fool this technology by being a twin? Think again! Kyle Robbins, our Graphic Designer, is a triplet. We tested Name.com Face Login with all three. Kyle quotes “All my life people have confused me with my brothers. Name.com Facial Login knows that even though we are triplets, we all still have something unique about us. Face Login gives me an identity I never knew I had. I AM unique!”
Our dev team makesit rain positive change, although they cringe at being called “Rainmen” (yet you should see them play cards.) They’ve been cranking out web goodness and have made the following improvements:
Added more templates to the DNS management page,
Updated the account contacts & Domain contacts page,
Added more options to the Email Domains tool,
Added a way to stop a transfer from going out and
Updated account settings page.
As Product Manager Shannon says, “We pushed another exciting update to account management. There is now an Account Settings page where users can edit their contacts, enable or disable renewal notices, and edit default nameservers. Users could always do this stuff but it had previously been part of the Account Contacts page. This is what it looks like:
Meanwhile, Smitty, who’s in dev, heralded the nameserver changes:
This morning we are pushing an update to the nameserver management page. Customers will now be able to select nameserver templates from a dop down. The templates are dynamically generated nameserver groups based upon the nameservers that the customer is currently using for all other domains in the account. Please let us know if you notice anything out of the ordinary.
And this with some interesting new terminology:
Today we are deploying the new contact management pages. All of the previous domain/account contact management functionality is still intact, only with a slicker, cooler, more manageable, form validator-able, tabable upgrade! Most notably, we have integrated Google’s phone number validation library, which should help international customers get those pesky phone numbers updated correctly. As always, please let us know if you run into any issues.
See “tabable” in action…
And here’s a note from P-Fro in dev about the transfer cancel feature:
We’ve just pushed a feature where customers can cancel a transfer out of Name.com from the domain management page…
To come: Revamp of domains list page that will include new features like a ways to search and categorize/group domain names.
So Nick in dev made the exciting announcement about how you can now sync your domain name expiration dates. But before I pushed it live to the blog, I wanted to make sure he’d included everything…
That about sums up the name.com experience: Ultimate User Enjoyment. Nick explains:
Friends, Romans, Countrymen, and Legend (you know who you are),
We’re rolling out a new tool that will allow users to sync the expiration dates for their various domains. As of right now, this option is only available for .com and .net domains (sorry Henrik, you can’t sync your .se domains just yet).
On the page, the user will be able to select the new expire date, then select the domains that they want to have that new expiration date. Then, they must hit “Apply” for those sync products to be added to the cart. It will not allow the sync date to be before the current expiration date, or further out than 10 years (70 dog years) from the date of the sync, not the date of the current expiration date. The pricing is $1.15 per sync month, and if the sync is longer than a year, the users domain will be sync’d to the correct date of the year current, and then renewed until the desired expiration date is achieve. I really hope this makes sense and doesn’t come across a Jared-esque rant.
This post is about Minimum Viable Product, or MVP. This little acronym gets tossed around a lot here at Name.com, because we like innovation. Innovation is a wonderful thing, but it can be somewhat of an organizational nightmare for product management.
Our process goes like this: We decide that we want to add a new feature to a product or the website, but we’re not entirely sure how it’s going to work. We get a bunch of idea-driven stakeholders in a room, and we brainstorm about the feature. Suddenly we have 26 features that are all totally awesome, and we’re going to fit them all into one scoping document and one sprint to be finished in the next 2 weeks with only one developer working on it.
And that’s how Homer came up with PageZen.
Oh, and it won’t need any testing either. This is GREAT! All the stakeholders leave the meeting feeling warm and fuzzy about the events that just transpired. We have so many neat ideas, and we can’t wait to see how they turn out.
It’s only once it’s in writing that we realize what is quite obvious to an outsider. All of these ideas are awesome! We can accomplish each and every one of them. It’s just going to take our entire development team 4 months. This is where MVP comes in. What can we push out in the shortest period of time with the minimum amount of development that will still be of value to the user?
We go back and forth until we strike that balance, and when it’s all said and done we have a solid spec that can be completed in one sprint by one developer. The agile process will tackle the testing, and we push the 23 other features to the back burner. They’re not in the sprint, but they’re not forgotten either. They’re hanging out in the development team’s backlog, waiting for iterative development to pick them up.
Analyzing and trying to produce an MVP is not only good for iterative development, it’s a solid business decision as well. We think we know what our customers want and sometimes we do, but sometimes we are way off base. Getting a product out the door and allowing your customers to bang on it allows you to track its desirability and also ask for their feedback on the features they want to see. You might be surprised to find that the features they want are nowhere in your list that landed in the backlog.