- .bid
- .download
- .date
- .loan
- .men
- .party
- .stream
- .trade
- .win
You could probably get away with using a few of these for a home network, though some would be kinda strange (.men? .loan?).nets and .coms increase in price too, but they don't tend to jump by 100% in a single year like these novelty ones, which were created purely to make money for the registry.
e.g. https://tld-list.com/blog/tld-wholesale-price-increase-2023
TLD Old New Percent Date
.reviews $17.00 $40.00 135.29% 2023-10-04
.furniture $38.00 $80.00 110.53% 2023-10-04
.faith $4.98 $9.98 100.40% 2023-09-04
.racing $4.98 $9.98 100.40% 2023-09-04
.review $4.98 $9.98 100.40% 2023-09-04
.science $4.98 $9.98 100.40% 2023-09-04Define 'cranked'.
I spend way more in a bar in one night than on my domains yearly, so I always find 'oh I need one super-duper cheap, below $2/y otherwise it's way too much' comments a bit.. too frugal.
Sure anyone would be, but... maybe don't choose .furniture[0] as the TLD for your own small private LAN DNS and don't have the unpleasant surprises?
The prices for the registrations (and renew) are going up steadily (just like everything else? inflation is a thing), but there is always an option to get the information about the renewal price upfront and maybe even use the multi-year sale.
Just looked in Dynadot's CSV, there are ~100 TLDs with sub $10 renewals and additional ~100 with < $15.
Also dug my records[1], privacy is baked in now, so the total effective rise is $1 for `.one` and... -$2 for `.com`.
[0] https://news.ycombinator.com/item?id=40571805
[1]
date created: 2015/08/20
<placeholder>.com - domain renewal
1 year ($10.99)
<placeholder>.com - domain privacy
1 year ($3.00)
PAYMENT
final cost: $13.99
date created: 2016/07/21
<placeholder>.one - domain renewal
1 year ($10.99)
<placeholder>.one - domain privacy
1 year ($3.00)
PAYMENT
final cost: $13.99
Date created: 2023/09/08
<placeholder>.com - Domain Renewal
1 year ($11.99) $11.99
Date created: 2023/10/16
<placeholder>.one - Domain Renewal
1 year ($14.99) $14.99The public PKI is built on the public DNS system. If you want a cert to be trusted by default and don't want to bother with your own internal PKI then you need to leverage the existing public infrastructure, which doesn't give it away as a free beer but sells it.
> you need to leverage the existing public infrastructure, which doesn't give it away as a free beer but sells it.
No, it's the opposite these days. The existing PKI these days is free (Letsencrypt and others), but getting a public domain that any browser-acceptable CA will issue certificates for isn't. Your domain registration/renewal fees don't pay for that PKI.
I think it's urgently needed for browser vendors, the IETF etc. to get together and figure out a solution for accessing "mymediocreiotdevice.home" without a barrage of "zomg no HTTPS!!", "zomg self-signed cert!" etc. warnings, as these will only desensitize users further to actual problems on publicly-accessible sites.
This is what I said in the first place - public DNS is not free. The costs to get in range but the minimal isn't that much ($5/year to be precise), so the question is between any amount at and no at all.
I haven't bothered doing DNS auth to get certs since I started using paid domains.