@stefan After Google domains shutdown, I moved all of mine over to WordPress. The prices were comparable. The only issue is that they wouldn't let me transfer over anything that was considered a premium domain. I've heard that cloudflare has pretty good prices for domain name renewals. They have the same premium domain limitation, though.
I suddenly remembered that the domain name registration for Twitter.com was set to expire on January 21, 2024. I had taken a screenshot of this last July.
Curious, I went to see what happened and… the current management is SO CHEAP that they only renewed the name for one extra year… and took care of this 4 DAYS before the expiration 🙄
Wrote a couple of standalone scripts to download and parse the expiring, pending delete, and platform-exclusive auction lists provided by NameJet and SnapNames. Let me know if you have any issues running.
You type in to your browser's address bar example.com and it automatically redirects you to the https:// version. How does your browser know that it needed to request the more secure version of a website? The answer is... A big list. The HTTP Strict Transport Security (HSTS) list is a list of domain names which …
You type in to your browser's address bar example.com and it automatically redirects you to the https:// version. How does your browser know that it needed to request the more secure version of a website?
The answer is... A big list. The HTTP Strict Transport Security (HSTS) list is a list of domain names which have told Google that they always want their website served over https. If the user tries to manually request the insecure version, the browser won't let them. This means that a user's connection to, for example, their bank cannot be hijacked. A dodgy WiFi network cannot force the user to visit an insecure and fraudulent version of a site.
After about a decade of use, the list is now 14MB in size, with around 130,000 entries in it. You can view the list online or download it.
The most popular (over 1,000 entries) TLDs / Public Suffixes are:
Rank
TLD
Entries
1
com
43,236
2
tk
19,022
3
de
5,216
4
org
4,731
5
gov
4,507
6
net
4,410
7
ga
4,326
8
nl
2,671
9
cf
2,458
10
ml
2,271
11
co.uk
2,139
12
fr
1,714
13
ru
1,516
14
eu
1,283
15
com.br
1,226
16
gq
1,225
17
io
1,215
18
com.au
1,202
19
it
1,103
20
cz
1,004
After .com, the free .tk domain names absolutely dominate. I wonder how many of them are fraudulent?
There are 2,676 .uk domain names - only 537 of which aren't on .co.uk.
Going a bit further, there are 418 IDNs (which start with xn--).
And about 187 have "porn" in the domain.
You can't really extrapolate much from this as a data set. Lots of the domains seem to have expired or otherwise no longer work. Reading around https://hstspreload.org it notes that because this list is hard-coded into Chrome it can take months before a site is added. Similarly, removal can take a long time as well.
I can't help feeling that there should be a better way to manage all this though.
At ZERO GmbH, we're managing a lot of #AMPS Nodes (see: https://zero-iee.com/en/products/). Most of them are connected to our management VPN. Each of the nodes has a unique identifier (serial no.).
We've set up an internal DNS server that resolves their serial bumber-based FQDN and returns the corresponding VPN IP address. Thus it's easy to find the correct VPN and IP address to start maintenance or troubleshooting :-)
Our requirements on a DNS Server are quite low. We could have picked THE ONE, the only, the allmighty Bind DNS server - but instead we tried something different:
Yadifa. https://www.yadifa.eu
Yadifa is a less-known DNS server implementation by EURid - the nonprofit organization that powers the .eu top level domain!
We were surprised of the simplicity of Yadifa and had our DNS Server up and running in minutes! If you're looking for an easy to configure DNS server, check it out.
@zeroiee "We were surprised of the simplicity of Yadifa" Probably because bind is old and packs LOTS of things, including being both recursive and authoritative all in the same source code (you can then configure it to be just one or the other face, as prefered). Yadifa is authoritative only. Note that you have also as "newer" ones, KnotDNS and CoreDNS in go; dnsmasq is also a very useful "swiss army knife".
@pmevzek (ZERO developer speaking). Yes, I run bind for some reverse DNS zones and it's working fine, but I had a feeling that there must be something more sleek, more "made for this purpose". Yadifa looked like a perfect match. I've also seen KnotDNS (but didn't really like the Lua style config syntax) and CoreDNS. Maybe CoreDNS is worth another look. I'll check it out :)