Sad as it is to say, there are a lot of scams out there that revolve around domain names. One of the most common domain scams is phony renewal notices, usually communicated via phone, snail mail, or email. So when we recently received a phony domain renewal email to our marketing account, we figured it was the perfect opportunity to show you how to spot a domain registration scam and avoid falling victim to it.
What’s the difference between HTTP and HTTPS?
You may have noticed during your various online escapades that the ever familiar HTTP in front of a domain name occasionally turns into the less familiar HTTPS. Depending on your browser, this may also be accompanied by a color change in the address bar to green, a lock symbol, or other signs that make the URL field look different from what you’re used to. What does it mean? Does it really make a difference?
A note on Name.com’s policies and how to spot phone scams
We’ve received reports that several of our customers have been contacted via phone by a scammer who claims to be part of the Name.com support team. This individual tells his or her target that their domain is about to expire and that they need to renew it by giving their credit card information to the person on the line.
This is a scammer, and you should not provide him or her with any information if you are contacted by them.
Prevent domain hijacking with these security tips
If you buy a domain name, it’s rightfully yours for as long as you continue to renew it. But in some unfortunate incidents, domain names are stolen by a hacker and either resold or used for nefarious purposes. Instances like these are called domain hijacking, and although they don’t happen often, they can be a serious headache deal with.
The best way to prevent domain hijacking from happening to you is to be proactive about your account’s security. By following these tips, you can do your part to keep your account—and your domains—safe.
Why you need privacy protection for your domain names
If you’re new to websites, you may be unfamiliar with some of the additional services that registrars offer when you purchase a domain. One service that can be especially confusing is domain privacy protection. What is it? And is it really necessary?
With the abundance of news about compromised cyber security and hacking schemes, it’s natural to want to take extra precautions to keep your online information safe.
Two-Step Verification keeps your account extra secure by requiring a time-sensitive code in addition to a traditional login. As opposed to solely relying on a username and password, which can be guessed or figured out by an experienced crook, Two-Step Verification adds an extra layer of security.
Better yet, getting Two-Step Verification set up for your Name.com account is a simple task that can be done in a matter of minutes. Let’s walk through the steps.
We recommend Two-Step Verification to everyone, as it’s the most fool-proof way of keeping the domains in your Name.com account secure – and it’s totally free. It’s especially important for people who have hundreds or even thousands of domains in their accounts, as they’re more likely to be targeted by bad dudes trying to hijack domains.
The basics of our Two-Step Verification process are still the same—create a unique credential for your account, and then use a smartphone app to generate unique login codes—and it remains a totally free feature for all Name.com customers. However, if you were previously using Namesafe we’ve made some changes that will require you to update your verification credentials by March 5, 2015 to keep your account secure.
This post is meant to give you recommendations on how to prevent a potential domain hijack before it happens, because once a domain transfers to another registrar it can be difficult to re-acquire, especially if the transfer was in compliance with ICANN policy. If the registrar is not willing to transfer the domain back into your control then your options for recovery become very limited.
On Wednesday news broke that there’s a widespread, potentially harmful vulnerability that affects the computer systems that a lot of us use every day, including OSX and Linux. It’s called the Bash Shellshock Bug. Here’s a quick rundown of how the bug works, who it affects, and how we’re handling it at Name.com: