Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 fonts
Octocat-spinner-32 images
Octocat-spinner-32 javascripts
Octocat-spinner-32 stylesheets
Octocat-spinner-32 CNAME
Octocat-spinner-32 README.md
Octocat-spinner-32 STAR_localtest_me.pfx
Octocat-spinner-32 STAR_localtest_me.zip
Octocat-spinner-32 index.html
Octocat-spinner-32 params.json
README.md

localtest.me

Credits: Scott Forsyth, Imar Spaanjaars, others

Save this URL, memorize it, write it on a sticky note, tweet it, tell your colleagues about it!

localtest.me (http://localtest.me)

and

*.localtest.me (http://something.localtest.me)

If you do any testing on your local system you’ve probably created hosts file entries (c:\windows\system32\drivers\etc\hosts) for different testing domains and had them point back to 127.0.0.1. This works great but it requires just a bit of extra effort.

This localtest.me trick is so obvious, so simple, and yet so powerful. I wouldn’t be surprised if there are other domain names like this out there, but I haven’t run across them yet so I just ordered the domain name localtest.me which I’ll keep available for the internet community to use.

Here’s how it works. The entire domain name localtest.me—and all wildcard entries—point to 127.0.0.1. So without any changes to your host file you can immediate start testing with a local URL.

Examples:

http://localtest.me 
http://newyork.localtest.me 
http://mysite.localtest.me 
http://redirecttest.localtest.me 
http://sub1.sub2.sub3.localtest.me

You name it, just use any *.localtest.me URL that you dream up and it will work for testing on your local system.

More details

Read the introduction by Scott Forsyth

Something went wrong with that request. Please try again.