> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loadforge.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Verification
> About verifying Hosts on LoadForge
LoadForge requires that you add and verify hosts before you can run tests against them. This is to prevent users from running tests against websites or services that they do not own.
The process is very quick and requires either a simple meta tag or a file placed in your application's public directory.
**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
The meta tag method requires adding a `loadforge-site-verification` tag to the header of your website or application.
**Steps:**
1. Copy your unique verification code from the LoadForge dashboard
2. Add the following meta tag to your site's `` section:
```html example.html theme={null}
```
3. Save and deploy your changes
4. Click "Verify" in the LoadForge dashboard
This method is best for websites and web applications where you can easily modify the HTML.
The file verification method requires placing a text file at the root of your web server.
**Steps:**
1. Create a file named `loadforge.txt`
2. Add your verification code as the only content in this file
3. Upload the file to your web server's root directory
For example, if your site is `https://test.com`, the file should be accessible at `https://test.com/loadforge.txt`
This method is ideal for APIs or applications where modifying HTML headers is not practical.
The DNS verification method uses a TXT record to verify domain ownership.
**Steps:**
1. Add a TXT record to your domain's DNS settings
2. Use `loadforge-site-verification` as the record name
3. Set your verification code as the record value
The TXT record should be added under the host you're trying to validate. For example, `loadforge-site-verification.loadforge.com` must contain your account validation key.
### Lookup Example
```shell nslookup theme={null}
❯ nslookup
> set type=txt
> loadforge-site-verification.loadforge.com
[..]
Non-authoritative answer:
loadforge-site-verification.loadforge.com text = "8ee17273640295c9[..]"
```
```shell dig theme={null}
❯ dig loadforge-site-verification.loadforge.com TXT
> loadforge-site-verification.loadforge.com
[..]
loadforge-site-verification.loadforge.com. 300 IN TXT "8ee172736402[..]"
```
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 validate `example.com`, we will automatically validate any subdomains under that domain, such as `dev.example.com`, when you add them.
## Alternative Validation
If you need to validate your domain manually, you can [contact us](https://loadforge.com/contact) or email [support@loadforge.com](mailto:support@loadforge.com). You will be required to prove ownership.