Kyle Rego

Why LinkedIn won't let me link my project to a .lol domain name

Recently I bought the domain name larder.lol for $1.80 (with a $6 TLS certificate too), which I thought was a pretty good deal, and I set up my project web app on that domain.

Today I wanted to link to larder.lol from a project on my LinkedIn page. I found that when I add the link larder.lol as a media to the project, LinkedIn changes the link to kylerego.net automatically. I tried multiple times and this happened every time.

Entering larder.lol as the link

Clicking “Add” in the above results in this (the thumbnail is the picture on kylerego.net):

After clicking add, it shows an image and title from kylerego.net

Why does that happen?

It’s because both websites are running on the same VM that has one IP address–both domain names are pointed to the same IP address. With Apache named virtual hosts, the ServerName directive is used to route requests to the correct virtual host based on the domain name in the request and both virtual hosts are using port 443.

At first I thought that LinkedIn must be doing some check with the DNS records, where I enter larder.lol, LinkedIn finds that larder.lol points to the same IP address as kylerego.net, and changes the URL of the project to kylerego.net, but that seems like a strange thing to do intentionally. I guess however LinkedIn gets the thumbnail and title of the page causes this to happen, I don’t know the exact mechanism but it makes sense that it can happen knowing the setup of the relevant websites here.

Unfortunately, this unexpected experience is not a good sign to keep using .lol domain names, although I am not completely sure how relevant that detail is.

This project is maintained by KyleRego