But why??? We do this to prevent LoadForge from being used to DoS other websites. It helps prove you own the website or application.
Meta Tag
The meta tag we use is calledloadforge-site-verification
, and it needs to be placed in the header of your website or application. For APIs, this is often not appropriate, and the File method is recommended.
The final meta tag looks like this (with your unique verification code):
example.html
File Verification
The file check sends a request to your webserver for the fileloadforge.txt
. If your site is https://test.com
, then you would need to ensure that https://test.com/loadforge.txt
is accessible.
Once this file is returned with the verification string we provide, the test will pass.
The file must contain your verification code, the same as seen in the meta tag example. The code for the meta tag and the file is always identical.
DNS Verification
You may also verify your ownership with a DNS TXT record calledloadforge-site-verification
.
It must exist under the host you are trying to validate. For example, loadforge-site-verification.loadforge.com
must contain your account validation key as the value.
Lookup Example
Automatic Validation
We use the same verification tag for your account, regardless of the host. This means you can always use the meta tag or file we provide on any of your applications. This also simplifies adding hosts through the API, as you will know their validation code in advance. Additionally, if you validateexample.com
, we will automatically validate any subdomains under that domain, such as dev.example.com
, when you add them.