- Joined
- Sep 11, 2002
- Messages
- 1,495
- Reaction score
- 0
Has anyone else had to do "defensive" snaps/regs on certain names, just to ensure that the REAL domain name you want isn't hijacked while you wait for it to drop? It strikes me as a bit exotic, but this is the second time I've had to do it in the last couple of months. The names don't stink, but they're a bit out of my way sometimes.
Ok, I'm hesitant to go into detail, but I'll try as most people will have absolutely NO CLUE what I'm talking about.
Here's the scenario:
1.) You have found a domain name that is soon to expire or expired. You like the name. Let's call the name: "COOLNAME.COM", and it will expire in 1 month.
2.) Many good names are "snapped" very early in advance, so some forethought is important. Is the name really going to drop? Typing it into the browser reveals that "COOLNAME.com" is already NOT resolving to a website (ok, this is promising). Using the whois record, maybe checking the website of the admin contact will tell you if it is a corporation or small business, or if they are even around any more. These bits of info may help in determining if they are really letting the name drop, or if it is a big company with an oversight that may be corrected soon. Let's say the website of the admin contact is: "[email protected]"
3.) You find that the website of the admin e-mail (WEBADMIN.com) is down. Not a big deal, as not every domain name has a website up at it.
4.) With no website, you will need to look further. The whois of WEBADMIN.com may give you a company name to check or another website to scout out.
5.) Uh, oh. The admin contact website (WEBADMIN.com) is not even registered anymore! You can still research the identity of the owner more through Google or Archive.org maybe, but you have a very real problem right now. While you may be looking to register COOLNAME.com through a snap in a couple of months, someone else may in the meantime register WEBADMIN.com. This may not be a big deal, but considering the rampant nature of domain hijacking these days, that person may have registered WEBADMIN.com, and suddenly... suddenly COOLNAME.com may get transferred before it expires (hijacked by the new owner of WEBADMIN.com), and you will be out of COOLNAME.com. You may start your complaints, but more than likely, you will simply be out of luck.
6.) You put a snap on COOLNAME.com anyway, but you are current "exposed", as the current admin e-mail domain is sitting out there as a security hole waiting to happen.
7.) You register/snap the admin e-mail domain name (WEBADMIN.com), while you wait for COOLNAME.COM to drop. By doing so, you avert the possibility of having the name you are waiting for "hijacked", and can wait for the "drop" with perhaps an increased feeling that it will actually drop.
Again, it may be an exotic procedure, but I've seen strange things in the last year. For the most part, people don't talk about it, and when they do, things seem quickly quieted up and I'm left wondering how often these things happen uncontested. I don't snap many names on a regular basis, so when things "go bad", it can be more of an upset for my plans (than it may be with the average domainer).
Network Solutions had a serious problem for a while, as people would "forge" e-mail transfer requests in "stealing" people's names (they began adamantly requesting that people use different authentication methods than their insecure "MAILFROM" method). These days NetSol has transitioned away from their old architecture, though other registrar transfers are handled only slightly more securely, with security issues will always remaining in the balance between "ease" and "safety".
I worry.
~ Nexus
Ok, I'm hesitant to go into detail, but I'll try as most people will have absolutely NO CLUE what I'm talking about.
Here's the scenario:
1.) You have found a domain name that is soon to expire or expired. You like the name. Let's call the name: "COOLNAME.COM", and it will expire in 1 month.
2.) Many good names are "snapped" very early in advance, so some forethought is important. Is the name really going to drop? Typing it into the browser reveals that "COOLNAME.com" is already NOT resolving to a website (ok, this is promising). Using the whois record, maybe checking the website of the admin contact will tell you if it is a corporation or small business, or if they are even around any more. These bits of info may help in determining if they are really letting the name drop, or if it is a big company with an oversight that may be corrected soon. Let's say the website of the admin contact is: "[email protected]"
3.) You find that the website of the admin e-mail (WEBADMIN.com) is down. Not a big deal, as not every domain name has a website up at it.
4.) With no website, you will need to look further. The whois of WEBADMIN.com may give you a company name to check or another website to scout out.
5.) Uh, oh. The admin contact website (WEBADMIN.com) is not even registered anymore! You can still research the identity of the owner more through Google or Archive.org maybe, but you have a very real problem right now. While you may be looking to register COOLNAME.com through a snap in a couple of months, someone else may in the meantime register WEBADMIN.com. This may not be a big deal, but considering the rampant nature of domain hijacking these days, that person may have registered WEBADMIN.com, and suddenly... suddenly COOLNAME.com may get transferred before it expires (hijacked by the new owner of WEBADMIN.com), and you will be out of COOLNAME.com. You may start your complaints, but more than likely, you will simply be out of luck.
6.) You put a snap on COOLNAME.com anyway, but you are current "exposed", as the current admin e-mail domain is sitting out there as a security hole waiting to happen.
7.) You register/snap the admin e-mail domain name (WEBADMIN.com), while you wait for COOLNAME.COM to drop. By doing so, you avert the possibility of having the name you are waiting for "hijacked", and can wait for the "drop" with perhaps an increased feeling that it will actually drop.
Again, it may be an exotic procedure, but I've seen strange things in the last year. For the most part, people don't talk about it, and when they do, things seem quickly quieted up and I'm left wondering how often these things happen uncontested. I don't snap many names on a regular basis, so when things "go bad", it can be more of an upset for my plans (than it may be with the average domainer).
Network Solutions had a serious problem for a while, as people would "forge" e-mail transfer requests in "stealing" people's names (they began adamantly requesting that people use different authentication methods than their insecure "MAILFROM" method). These days NetSol has transitioned away from their old architecture, though other registrar transfers are handled only slightly more securely, with security issues will always remaining in the balance between "ease" and "safety".
I worry.
~ Nexus