This morning I found that lvh.me is no longer responding to localhost and is instead resolving to 34.98.99.30<p>Looks like the domain has expired.<p>Anyone know who the owner is or how I can help in sponsoring getting this set back up again? It's a free tool, but it's used by a lot of developers.
Just did some testing and it seems like the latest Chrome and Firefox browsers both support *.localhost, so this is a good replacement.<p>Works also with port numbers, eg <a href="http://example.localhost:3000/" rel="nofollow">http://example.localhost:3000/</a>
I don't know lvh.me, but it sounds similar to nip.io and xip.io.<p>If you don't want to rely on a free service to point to your localhost, I recommand ngrok.io. I believe they have a free plan. It works with your virtual hosts as well :-)
This seems like a terrible practice, localhost should resolve to localhost a TLD of its own. Having some random entity controlling a domain at the .me TLD, and using that in a processes is just asking for trouble.
Not an answer to your actual question but you might be able to switch to <a href="https://readme.localtest.me/" rel="nofollow">https://readme.localtest.me/</a> instead.