71–80 of 189 posts
Earlier quoted context omitted.
Which registrar is recommended?
I personally prefer Gandi, but also use name.com and Cloudflare - haven't heard any horror stories about either of those 3 registrars.
I am a fan of NameCheap personally.
If you were hosting phishing sites then I'm glad they did this. You should have better controls.
I've seen domains like google5[.]$tld which contained a fake Google Login form, up for close to an hour with zero detects in VirusTotal and no detection by Google Safe Browsing itself. If Google fails at detecting phishing against their own brand, what chances do smaller shops realistically have? Here's the example I mentioned: https://twitter.com/urlscanio/status/1178043405529763841
Earlier quoted context omitted.
Namecheap dumping personal info without informing their customer ( https://news.ycombinator.com/item?id=18063667 ), Namecheap threatening to shut down a site if the customer doesn’t delete two images posted there within 24 hours ( https://news.ycombinator.com/item?id=14139288 )
Which registrar is recommended?
Earlier quoted context omitted.
> they support a lot of the new TLDs like .io which is also a lot cheaper. You might want to pick another example, .io is 23 years old [0] [0]: https://en.wikipedia.org/wiki/.io
For some reason people keep forgetting that io stands for indian ocean and is actually a regional tld like co.uk .net .de etc Same with .ai fwiw.
Some random British company convinced IANA to let it run the .io domain for their own profit. Their operation of it has nothing to do with the interests of its exiled inhabitants (the Chagossians), the British territorial and military authorities, or the US military presence which constitutes the the territory's raison d'etre.
I think it likely that, one of these days, something is going to happen to the .IO ccTLD operators. Their rights to it are very dubious, and someone else (the British government, the government of Mauritius, the Chagossians) could end up wresting it from them.
Earlier quoted context omitted.
Namecheap dumping personal info without informing their customer ( https://news.ycombinator.com/item?id=18063667 ), Namecheap threatening to shut down a site if the customer doesn’t delete two images posted there within 24 hours ( https://news.ycombinator.com/item?id=14139288 )
Which registrar is recommended?
I've been using them for years, and never had any technical issues...
The biggest hoster of phishing sites is Google.[1] Here's a list of major sites which have live entries in PhishTank.[2] Hosting phishing sites on Google Drive is very popular. Many of those are long gone, but PhishTank hasn't cleaned them out, so they're still listed. [1] http://www.sitetruth.com/reports/phishes.html [2] http://www.sitetruth.com/fcgi/ratingdetails.fcgi?details=tru...
To be fair, every platform which allows user-generated HTML pages suffers massively from phishing and most of them don't deal with it very well: Google, Microsoft, smaller players like Codebox and countless others. Then there's phishing on Dropbox, phishing on Google Forms, OneDrive, etc. Then you have phishing at all the various hosters like DigitalOcean, CloudFlare, etc. Even there you'll sometimes have IPs which h…
I used to contact nonprofits and small businesses which showed up on that list. Inevitably,they'd had a break-in. With some nagging, I could cut the size of the list in half.
I wonder how the domain registry community at large feels about this? ICANN exists, domains are subject to a legal agreement with ICANN, and it has customer-protection concerns surely?
GitBook CTO here: Our production domains (gitbook.com and gitbook.io) have been blocked and locked by our registrar (Google Domains). None of our infrastructure is impacted, all user content and databases are safe; our domains simply blocked by a heavy handed policy. As mentioned on Twitter, we are all hands working with Google to fix this issues ASAP. We'll then share an in-depth post-mortem https://twitter.com/GitB…
We've just published a postmortem: https://blog.gitbook.com/tech/post-mortems/06-20-gitbook-dom... let us know if you have any questions!
I don't expect google appreciates how devastating this, but that would change quite immediately if it happened to them.
Earlier quoted context omitted.
We've just published a postmortem: https://blog.gitbook.com/tech/post-mortems/06-20-gitbook-dom... let us know if you have any questions!
Seems like you should also move off of Google Domains, unless you have some compelling reason to use them.