4 ms·
I don't know where you registered your domain, but I have like 100 domains, and I've never been contacted about them (except by the registrar of course). Most o
by kuon 9y ago
I don't know where you registered your domain, but I have like 100 domains, and I've never been contacted about them (except by the registrar of course). Most of them have valid and router MX.
- throwanem 9y agoGoDaddy, and maybe that's my problem. On the other hand, I've been doing business with them for many years, and never had anything remotely resembling this happen before. I also didn't use whois privacy, but, again, I've made that choice on many domains before, and likewise never seen anything like this result from it.
- rtx 9y agoThis is due to a new business model. Where companies scrape ICANN data base for newly registered domains and then sell it to service providers.
- throwanem 9y agoThat squares with what I'm seeing, yeah - a lot of cheaply automated nonsense trolling for a few suckers. Is there anywhere I can look for more information on how this model works in detail, and how to avoid the same problem in future? It's a real pain in the neck. Thanks!
- rtx 9y agoBest way is to opt for whois protection in your first year or for first few months. Here is a mail I received offering the service. Hello, My Name is Prk Aa We are providing whois data in very low price Daily more than 100,000 domains are registered Reply Me with your contact number & skype id. Warm Regards Prk Aa
- throwanem 9y agoLessons learned, I suppose...
- Macha 9y agoExcept it's not new at all. Since I first got my email on my primary domain in 2008 or so I've had admin@, postmaster@ etc., Along with the address in whois all being spammed.
- saul_goodman 9y agoSome domains have been used as shit magnets and you can inherit that mess if you pick it up quickly after it's been dropped. I wouldn't believe it myself, until it happened to me. I've run small mail servers for various domains for years with only "average" amounts of spam. Then one time I picked up a personal domain of my handle (not this one) which I'd wanted for years and I discovered it finally was free. The moment I setup an mx for that domain I got a firehose of spam coming in to it. In fact it was so bad I had to unreg the mx and leave it for another year before it was worth doing anything email-wise with the domain. Just the bounce processing was driving cpu and bandwidth more than I cared to deal with, even if it wasn't receiving any local mail.
- throwanem 9y agoI checked the IP and the domain before I went with either of them, and their reputations are both clean, so I don't think that's it. I've definitely had that kind of trouble in the past, though.