But why? We do this to prevent LoadForge from being used to DoS other websites. It helps prove you own the website or application.
Verification Methods
Meta Tag Verification
Meta Tag Verification
The meta tag method requires adding a
loadforge-site-verification tag to the header of your website or application.Steps:- Copy your unique verification code from the LoadForge dashboard
- Add the following meta tag to your site’s
<head>section:
example.html
- Save and deploy your changes
- Click “Verify” in the LoadForge dashboard
This method is best for websites and web applications where you can easily modify the HTML.
File Verification
File Verification
The file verification method requires placing a text file at the root of your web server.Steps:
- Create a file named
loadforge.txt - Add your verification code as the only content in this file
- Upload the file to your web server’s root directory
https://test.com, the file should be accessible at https://test.com/loadforge.txtThis method is ideal for APIs or applications where modifying HTML headers is not practical.
DNS Verification
DNS Verification
The DNS verification method uses a TXT record to verify domain ownership.Steps:
- Add a TXT record to your domain’s DNS settings
- Use
loadforge-site-verificationas the record name - Set your verification code as the record value
loadforge-site-verification.loadforge.com must contain your account validation key.Lookup Example
DNS changes can take up to 48 hours to propagate, though they often take effect within a few hours.
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.