Domain verification is the process of verifying that your domain or hostname actually belongs to you, so we can load-test it.
For example, if you have an app hosted on
myapp.com you would like test requests from Loadmill to be sent to it during a load test. However, if we allow anyone to send requests to
myapp.com it could be abused by a malicious user to attack your servers by flooding them with requests.
The way this problem is solved is by using domain verification, a simple process in which you are asked to:
Go to User Settings > Domains.
Enter the hostname or sub-domain you would like to test in the text area at the top of the page and click Verify.
You will be prompted and asked to host a small text file, containing a Verification Token, on your server in order to prove you own your domain, e.g.
Once the file is hosted on your server, click Verify to complete the process.
If you have access to your site's DNS configuration, you can prove ownership without changing code on your server.
Note: There is no need to prove ownership of a sub-domain once its parent is verified. For instance, if you have already completed the verification process for
myapp.com you may load-test
blog.myapp.com as well.
It may also be used to enable crowsourced load testing, for high volume load tests.
If you do not want or unable to serve a file on your server, you can prove ownership of your domain via DNS.
According to the documentation of your hosting service or DNS provider, add a DNS record of the following format:
Name: The sub-domain you would like to test, e.g.
<VERIFY_TOKEN> stands for the Verification Token you were asked to serve in a text file. E.g.
You can make sure that the text record was properly added by looking it up using DNS lookup tools like this one - MxToolbox
Once the DNS record is set, click Verify to complete the process.
Note: DNS records may take a while to propogate, so if the verification initially fails, try again after a few minutes.