If anybody wants it, I compiled a list of Alexa's top 50 domains and their available TLDs:
https://docs.google.com/spreadsheets/d/1VaGA8344-13eGn9D1LAj...
Now with price!
I bought netflix.soy
171–180 of 272 posts
Re: I bought netflix.soy
#172Earlier quoted context omitted.
UDRP typically rules in favor of the holder of the unambiguous trademark in these kinds of cases. As an example, "Exxon Mobil" refers unambiguously to a single entity only, and has no other possible uses, so anyone registering exxonmobil.{anything} would lose if the company came after them. No one else has any right to that trademark, and ICANN enforces trademark rights on domains. If the trademark already existed wh…
What about .sucks? Couldn’t one claim free speech? https://www.forbes.com/sites/rogerkay/2015/06/29/saga-of-suc...
.sucks is a very special case. I wouldn't try to generalize anything going on there to other TLDs.
Re: I bought netflix.soy
#173Earlier quoted context omitted.
While it is an unwinnable case, there is a positive dollar amount to settling out of court.
Especially if you have a cute story like the MikeRoweSoft guy did.
He bought mikerowesoft.com though, not microsoft.soy. It would not have ended the way it did if he'd bought the latter. His case was a lot less clear cut than a blatant exact string match on an unambiguous trademark. Also, Mike Rowe is actually his name; Netflix is not this guy's name.
Re: I bought netflix.soy
#174There is a service ran by ICANN called the “trademark clearlinghouse”. It is a subscription service that trademark owners, e.g. Netflix, can use to be notified of any domain that is registered and may infringe on their trademark. It even allows for wildcard patterns in ongoing searches. How do I know this? Because i received a takedown notice regarding a domain I run to sell background job licenses (oban.dev). The bu…
Was it from the Oban distillery? Trademark issues aside they make a great whisky.
Indeed. It was from their parent company. I’m a fan of their scotch, so it’s a little bitter sweet.
Re: I bought netflix.soy
#175Somewhat off-topic, tinyprojects.dev and netflix.soy both have DNSSEC, is this required for some of the newer TLDs (like how .dev has mandatory HTTPS preloading)?
Just it's rare to see it in the wild.
Re: I bought netflix.soy
#176“I was just a soy boy”
Re: I bought netflix.soy
#177I bought space.sex
Re: I bought netflix.soy
#178Earlier quoted context omitted.
> they instantly became unavailable the moment I tried to do so. The cynic in me thinks that Google has a special check for those and renews it themselves if someone tries My guess is that they were never available and there are doing a poor job of figuring out which domains are taken and which are not. I've been this in several other domain name search sites too, especially if there is no nameserver for a registered…
Which is most likely because registries are known for having poor infrastructure. If registrars can't see the name is taken from the registry, they will default to available. I worked on some registrar-related stuff years ago now and even at that time, Verisign was known for having poor support of providing information about .com registrations.
> Which is most likely because registries are known for having poor infrastructure.
If people only knew that the internet was held together with bubblegum and duct tape...
Every fundamental layer has just crazy / old legacy foundations that are just incompatible with safe systems. Really opened my eyes when I saw how telco routing worked at the lowest levels.
Re: I bought netflix.soy
#179Earlier quoted context omitted.
I remember seeing a NIC that did this with their TLD. But I can't remember which one :/. I would love if someone finds it.
I think it's pretty common. Our national NIC does it: http://dk redirects to their website.
Surprisingly, going to http://dk redirects to https://www.penguin.com.au/browse/dk for me. How strange (I've never visited the penguin website before this).
Re: I bought netflix.soy
#180Earlier quoted context omitted.
Infrastructure changes aren't even needed; Google already owns the .google TLD. All they would need to do is attach an A record to the root.
Sure, but why would they? Can you imagine all the search advertising Google would lose if they allowed just 'nike' and 'att' to resolve the websites in Chrome, rather than search results?
Did we just find the secret to beating google?