Price increase on .io on January 21, 2021
news.gandi.net
news.gandi.net
It was hell trying to find a reasonable domain for our new company (i.e. one that we would like to have in our email addresses forever). Only 5-10% of the domains we attempted were legitimately in use by some other business or individual. Everything else is a fucking godaddy parking page offering their domain realtor scam experience.
Edit: Looks like it's $120 to pay for a "broker" now to contact the owner and then a 20% commission on top.
GoDaddy has a free monitoring service [1] where you add the domain(s) you are interested in and it will email you each time that domain WHOIS data is updated. This is very useful to get notified when a domain name is about to expire and then get deleted (redemptionPeriod, pendingDelete). Over a 5+ year time period, quite a few domain names I was monitoring were eventually dropped by their previous owners. These weren't highly sought after, but your local insignificant city .com, some rather unique first/last name...these type of domain names.
[1] https://www.godaddy.com/help/setting-up-domain-monitoring-57... (not affiliated with GoDaddy; not even using them as a registrar, but this tool proved useful for me)
Hopefully they've turned it around and actually working on useful services nowadays...
Does anyone other than GoDaddy have such a service? I would use this, but wouldn't trust GoDaddy not to steal the domain out from under me and then try to extort me for money. (Or just be obnoxious and try to advertise to me left and right.)
I've been using DomainTools's monitoring service [1] for years. I wouldn't trust GoDaddy with anything domain-related either.
[1] https://research.domaintools.com/monitor/domain-monitor/
The website on it had a ton of content too, which I never re-hosted anywhere else. Part of me wishes I had just hung on to it. milk.com is another one of those old holdouts where they guy is unwilling to sell it for less than 7 figures.
Nothing, absent a provision in the registration contract to the contrary, except the risk of everyone fleeing.
> Any laws preventing this?
No. Remember that [ccTLD - I originally wrote gTLD but those are a different thing, as corrected below] are assigned to the countries that they represent (or, in this case, the country that holds sovereignty over the named territory) so subject to their jurisdiction and there’s no real motivation for a country to pass such a law.
Bad image and massively losing the original customers.
>Any laws preventing this?
No, the gTLDs are allocated by ICANN which is a non-profit based in the US. As a whole, the domain name market follows very economically liberal rules.
I just remember that ICANN board was part of a recent .org story [1].
Domains are dominated by the long tail. Some people have built multi-million dollar brands off the TLD, but how do you raise prices to take advantage of that without losing the 100,000 other registrations that will just churn away?
In your example there's a fair bet they'd lose 99% of their existing user base, and kill any new use acquisition.
Is there anything to stop them from raising prices on the most established domains while keeping the long tail at the same price?
E.g., some of the new TLDs already have "premium" pricing for dictionary word domains, is there anything stopping them from raising the price on dictionary domains after someone has started using them?
I registered a ".plus" domain for $2 a year for two years. It made a decent domain hack for a project.
After two years, the renewal price became $20-ish. The project had a new name by then, so I didn't renew.
The same happened for a personal Chinese domain (.网站 I think) that I had for a couple of years while I was learning Chinese.
You are pretty much bound to what the registry can do. Take it away, hike the price up, etc.
To contrast, the .io space entered at what, $50 USD? and continues to be expensive to maintain year over year, providing a natural monetary resistance barrier to the same three groups of people (spammers, squatters and hackers) and seems to enjoy a healthy respect amongst internet users; most consider it a tech-type domain space with tech worker dollars buying the domains for real sites, I even owned one for a brief period when they came out.
I don't know which point you were trying to make, but as far as I could tell that's the business model that's being followed by all vanity gTLDs.
The only nuance I've noticed is that there are a bunch of domains being sold for peanuts with the caveat that after a year or two it's price is hiked to somewhere in the range of 30-50$.
I read the contract carefully, there is nothing preventing Google from increasing the price to 10,000 or 100,0000. It’s my biggest fear.
My only hope is that Google wouldn’t do it from a PR perspective, which I think is a safe and fair assumption.
The real worry is they sell the rights to .dev to GoDaddy or somebody else, because then I am screwed.
Google is one of the best things to happen to domain registrations. I highly recommend them. Even though I’m contractually exposed, to date, Google have been conducting themselves very well in the domain registration market.
One of the great things about .com is that there is a contractual cap on price increases. However the domain I bought would cost in the 10s of millions if it was a .com; so at 1,000 per year, it’s a good deal for the .dev version as long as they don’t significantly increase it (I’m okay with 10% per year increases).
Not really… There are many reputable ones. Gandi, namecheap and cloudflare are ones I can immediately think of. It’s just that some shady ones like GoDaddy do a lot of marketing.
Thats Google lobbying laterally through other industries but you just can't see it
I see Google Domains as a strategic division that supports their cloud services and Google Suites (note how Amazon also sells domains now, I think and hope they both see it as a necessity and don’t kill it like other Google projects they have abandoned).
I don't know much about the pricing of domains, so please excuse my ignorance.
Isn't that just due to the fact that your name was already taken on .com so you had to use a TLD, where is was still free? The 10s of millions you don't have to pay to registrar, you have to pay it the current owner of the domain, who like an owner of anything can dictate the price.
If that is correct, then how is 'google one of the best things to happen to domain registrations'? I guess this is not refering to pricing, because 1k$/a sounds like a lot of money for a domain.
Re pricing, I’ve noticed a few others bringing it up on 1,000 per year. This is a premium domain and instead of some scalper grabbing it up, by setting the annual price high, an actual end user like myself gets to buy one. In a perfect world we will be the first to snag up a domain, but this model of charging premium prices for domains, as long as it’s not exorbitant, works better for both end users and registrants.
1,000 sounds a lot per year, but when the .com is in the millions, it’s much fairer.
I don't understand how it can be argued that arbitrary price hikes works better for those who have to pay those arbitrary price hikes, specially if it's under a scheme where anyone can swipe your domain out of your hands regardless of how much you've invested in it without you being fairly compensated for it if their pockets run deeper.
Also it would kill their brand equity and the overall value of the extension, so I am hopefully for considerable price increases of 10% per year but not 50% or 100% etc.
The economist in me had to struggle to remember that if the prices are smart, it will lead to allocative efficiency. But it still feels a little ugly.
The key thing about .com is that once you buy the domain, the annual registration fees are more or less nominal — that’s what allows for very high sale prices. If I could buy my .dev name in .com for even 10,000 I would do it. Alas it is easily in the millions, IMO at least 10m+ as apart from protection for future material hikes in registration fees, .com is still THE gold standard.
For me, it made sense because I am actually using the domain, and I can make it my brand name, eg “Name.Dev” incorporated. This helps me from a trademark perspective as well, so for a small time guy with an idea, it’s a great feeling to get a chance to get a good name that I can put to use.
However I am hopeful it has a strategic purpose - for anyone using Google Cloud Services, it would be more convenient to have the domain registration bundled in. Similarly, Google sell you you@yourdomain.com as an add on in Google Suites.
As a user of both domains.google and namecheap, I'd recommend namecheap.
Usually, in both the cases, I immediately move registration to Cloudflare-run registrar.
I’ve heard good things about namecheap too.
Except, of course, for the lies they used to enter the market[1].
Repeated throughout: "Members of the public will not be able to register domain names in this new gTLD."
1. https://gtldresult.icann.org/applicationstatus/applicationde...
Wonder why this isn't more widely known?
My first thought was, I should pre-pay for the next 9 years now to lock it in cheap... then I looked at the price I pay now, 15.88$ and I paid about 4$ initial registration.
Honestly there's no rush, it's a minor price increase, and I expect things to get more expensive as time flies anyway, that's what happens to literraly every subscription I pay (rent, watter, energy, council tax, internet, phone, email are all "subscriptions" I pay and all of them have increased in price, and will undoubtedly increase again). Not that there's anything you can do about it, it's the "cost of doing business".
I'll have to consider what's the lifetime of this domain, should I pay now, or am I going to throw it away in a few years/months for something else. I'll probably keep it as it's a good one, and I'll put an alarm for the 4th so I have enough time to think this through.
The `.io` price increase looks a bit bigger relatively speaking, but nothing earth shattering... so try following the same logic as I detailed above.
Now the question: how often do these increase?
With respect to .io renewal on Gandi.net based on personal records:
US$35.00/yr through 2018
US$38.00/yr (+8.6%) into 2019
US$42.18/yr (+11%) into 2021
If I recall correctly, .io renewal was limited to something like 1- or 2-year intervals not too long ago; this appears to have changed, but I'm unsure when that happened.History of British Indian Ocean Territories: http://citizen-ex.com/stories/io
Anyone building a brand atop a ccTLD with this kind of history is taking a huge risk.
https://en.wikipedia.org/wiki/Expulsion_of_the_Chagossians#2...
PS I think it could a good idea to require some reason when downvoting, otherwise sometimes the context for doing that is completely unclear.
This is completely wrong. BIOT includes these islands where the native people were forcibly removed and the story is terrible.
https://en.wikipedia.org/wiki/Chagossians
https://en.wikipedia.org/wiki/Expulsion_of_the_Chagossians
It's not like this hasn't been discussed many times on HN before. I own a .io but come on!
Of course "native" can be arbitrarily limited to mean 1000s or 10,000s of years, but even after slavery those people lived there for at least five or six generations. So from the perspective of the people being forcibly removed, getting their pet dogs gassed by the military, it really wouldn't fucking matter.
And the Wikipedia article says they're "native", which you explicitly claimed was not the case.
What happened to .web ?
Verisign CEO said in their last investor conference that it will be coming soon but then all record of that was deleted from the web.
I've been using the 'casa' gTLD (the only others I see that are relatively bargain bin are 'link', 'site', and maybe 'click').
I don't need a brand. I just need to type something in that's not the IP address of my VPS...
However, if I want to have {my last name}.tld, is there any gTLD that would be unlikely to jack up the price? I actually have {my last name}.casa for this reason.
Unfortunately {my last name}.{com,org,net} were all registered when I was in diapers. I'm assuming that the land of gTLDs is the wild west of potential price shenanigans, but I'm wondering if I'm wrong.
Been here, done what you're doing, there's a .com out there with a fun and interesting name which somehow resonates with your personality. Think long term - avoid trademark/copyright branded words in the name, avoid being too narrow in case your hobby changes, easy to type and spend some time really thinking about plurality - I've discarded a lot of ideas simply because it would lead to other people going "was that with or without an (s) on the end?" - same with double-letters in the middle, just avoid them. I try and focus on 5-6 syllables max which break on natural language barriers (English).
For Google the bad PR would outweigh any benefits, so I think it’s the safest option.
However if you just want a name, .com is the best if you don’t care about a not so great name.
I do recommend .dev for developers if they can get a good one for their personal use / site, for the reasons you mention.
Go to Google domains, there’s an option to see all available domain endings with your chosen name, you can see if there is another that works better for you? Eg .xyz or.app etc
I should say that I am more attached to my first name than my last name because the former is slightly more special and thus more "unique" (also it sounds cute when people say it in English).
I also got https://lastname.dev too.
And lest you think you could just use your https://fullname.dev ... nope, already got it as well.
Reminds me of how I thought I was being clever by picking the facebook "shortname" of /forename.surename!
So if you really have thorny questions that need answering about how exactly certain complicated parts of the domain lifecycle work, you can just dive into the source.
Sure, there might be other requirements, and it's not clear what the exact use case is, but it also might be useful.
That's actually a fun exercise to come up with these use cases.
Not quite, you just need somebody acting as a local point of contact, and a number of registrars will offer this as an additional service for a small fee.
- TLDs with more than average marketing tend to not bring many surprises. .club, .blog, .co, .dev.
- TLDs run by companies with TLD portfolios tend to remain supported relatively as well. Donuts and Porkbun are examples.
- avoid abused TLDs such as .xyz. If a domain is sold at $0.80, that's a good sign of one. This 0.80 was registry pricing (not registrar eating costs), and companies behind them did very bad things to say the least. Alpnames for example was shut down by ICANN because if this. And you know how much ICANN doesn't care about people, judging by the .org scandal.
In my opinion, the safest ones are from your own country NIC, a generic TLD like .com or .net, or subdomains from an organization (js.org, eu.org, etc).
AFAIK there are zero guarantees. I think .com might have some pricing obligations, but all the good .coms are taken.
Don’t rely on ICANN. They’ve proven they don’t care about registrants with the .org debacle and when they let Uniregistry raise the price of domains for _existing_ registrants.
Donuts reclassifies domains to premium, but I’ve only ever seen it after a domain expires. Donuts raised some prices a few years ago, but let existing registrants keep their pricing AFAIK.
Assume there’s strength in numbers. Any attempt to increase prices drastically on .com, .net, or .org should result in a lot of backlash.
I also consider .dev and .app safe, or at least safer than the rest, because I don’t think Google is looking to turn a huge profit with them. They’re some of the most reasonably priced too.
The new TLDs could have been awesome if the registries weren’t so short sighted. They’re priced way too high to foster wide adoption. They should all be ~$10/year IMO.
Apart from a few sites like ticketmaster (not resolved) and discord (now resolved) not recognizing the TD I've had no major issues.
Your email reputation will likely be lower rated and likely be thrown in spam with major providers(Microsoft/Google) but that may also be because I am hosting my own email server.
TLDR; I feel like there should be a special dev-only TLD for certs that go on example code, which skipped all the certificate management limitations. Suggestions are welcome!
It is so cumbersome to provide WebRTC sample apps and tutorials that can be universally run for testing purposes. WebRTC requires HTTPS, and thankfully an untrusted self-signed cert will do for Firefox and Chrome (they will show a warning page that the user can accept); iOS further requires that the certificate is trusted (so no warning page is shown and the load silently hangs on an infinite reload loop, which is nasty if you ask me; to avoid this, you can manually install custom Root CAs to the device).
So, my WebRTC tutorials and demos need to include a self-signed cert that allows users to deploy in their LAN and do a quick test [0]. Browsers tend to accept "localhost" as a safe origin, but what happens with testing on LAN? I feel there should be some convention there, it's not very helpful to test a WebRTC application just on localhost.
To not assume any given LAN subnet, I create my self-signed certs for these domains [1]:
127.0.0.1
::1
localhost
*.test.local
That way, users can create a quick DNS redirection from some .test.local domain to their server (e.g. using avahi-publish command), install the root cert in iOS, and test from an Apple device.But I'd love if it was possible to just define a first level wildcard:
*.test
*.local
or similar.Actually the .local domain would be perfect! Thanks to mDNS, when available, all hostnames automatically get their <hostname>.local address, which would be great for an easier than ever setup. Alas, MacOS seems to reject first-level wildcards.
To add to the problem, these demo self-signed certs were created for 10 years, which is fine because I want to drop then on the Git repo and forget about them. But now the maximum allowed longevity for newly created certs is enforced to be a measly 398 days.
Why does all this need to be so needlessly complicated? I guess people will tell me to put in place a cert-renewal scheme, using some CI for all repos that contain demo code or tutorials, but that's highly undesired... There are even people suggesting that certs should live for just days or hours, I guess they are not thinking on this simple use case, for which I don't know if there is an escape hatch.
As mentioned in the TLDR; suggestions are welcome!
[0]: https://github.com/Kurento/mediasoup-demos
[1]: https://doc-kurento.readthedocs.io/en/latest/features/securi...
Nope (unless you own "an entire gTLD").
From the CA/Browser Forum's Baseline Requirements (v1.7.3) [0] (with a few links/references added):
--
3.2.2.6 Wildcard Domain Validation
Before issuing a certificate with a wildcard character (*)
in a CN or subjectAltName of type DNS-ID, the CA MUST
establish and follow a documented procedure that determines
if the wildcard character occurs in the first label position
to the left of a “registry-controlled” label or “public
suffix” (e.g. “*.com”, “*.co.uk”, see RFC 6454 Section 8.2 [1]
for further explanation).
If a wildcard would fall within the label immediately to
the left of a registry-controlled /1 or public suffix, CAs
MUST refuse issuance unless the applicant proves its rightful
control of the entire Domain Namespace. (e.g. CAs MUST NOT
issue “*.co.uk” or “*.local”, but MAY issue “*.example.com”
to Example Co.).
Determination of what is “registry-controlled” versus the
registerable portion of a Country Code Top-Level Domain
Namespace is not standardized at the time of writing and
is not a property of the DNS itself. Current best practice
is to consult a “public suffix list” such as the Public
Suffix List (PSL) [2,3, and to retrieve a fresh copy regularly.
If using the PSL, a CA SHOULD consult the “ICANN DOMAINS”
section only, not the “PRIVATE DOMAINS” section. The PSL is
updated regularly to contain new gTLDs delegated by ICANN,
which are listed in the “ICANN DOMAINS” section. A CA is not
prohibited from issuing a Wildcard Certificate to the Registrant
of an entire gTLD, provided that control of the entire namespace
is demonstrated in an appropriate way.
--[0]: https://cabforum.org/wp-content/uploads/CA-Browser-Forum-BR-... (PDF)
[1]: https://tools.ietf.org/html/rfc6454#section-8.2
Which surprises me. We even have IP address ranges defined for usage in examples in documentation... How come no TLD has been assigned for development purposes with relaxed requirements. Everybody needs to develop, as a first step before using an actual TLD. Just use .lan or similar!
Presumably, they didn't establish one because 1) that's outside of the scope of the BRs and 2) that's someone else's job, not theirs.
Regardless, as I pointed out in a comment [0] a few days ago on another thread, there are several such "special-use" domain names, although none specifically "for development purposes".
You won't be able to get a certificate signed by a PKIX CA for them, though; you'll just have to make your own.
--
In 2017, a Google security researcher took over the registrar, meaning he could update the zone files externally.
It was best practice to stop using .io at the time.
I heard a rumor that a more professional registrar got involved after that, but don't know the details.
Anybody know the story today?
The .org takeover attempt was recent. We've had bad .com leadership with Verisign. Domain registrars themselves can be pretty scummy.
In an effort to outperform the squatters, many gTLDs are pre-allocating "premium domains" and charging $500, $2500/yr for them.
There's lots of greed in domain names. Or opportunity. Depends upon what your perspective is.
I got my dream domain because I paid a premium for it to Google. I have to pay the premium every year, which I am fine with unless it increases too much, but I can imagine squatters said no to it because it’s hard to make a profit when you have shell out so much each year for the domain (whereas with .com it is just the starting price + nominal reg fees each year).
Because, personally, I was already bit in the ass by these price hikes from a gTLD. I started a personal website with a gTLD (.site) that I registered for about $1, and when it was close to expire suddenly the registrar demanded about $30 for it. I decided to jump ship to another gTLD and let the old one expire, to not support this kind of extorsion.
Since then I've been monitoring the state of the old domain name. Oddly enough my old domain name was parked as a premium domain, being on the market for close to $22, while other domain names from the same gTLD are sold for about $1.55.
In my opinion these gTLDs have been managed through extortion tactics, and I welcome any chance of discussing the subject.