Loadmill
Learn moreSchedule a demo
  • Introduction
    • Loadmill - AI - Powered Solution
    • Deviceless mobile testing
      • Capturing traffic with Loadmill MITM Proxy
      • Loadmill desktop recorder
        • Generating test flows
      • Installing certificate on mobile devices
        • iOS certificate installation
        • Android certificate installation
      • Configuring proxy on mobile devices
        • iOS Wi-Fi settings
        • Android Wi-Fi settings
      • Troubleshooting
    • What is an API
      • API - Data Fetching
      • Quick examples of API requests
      • What is an API endpoint?
    • API Server Testing
      • Contract testing
      • Regression Testing
  • Quick Guide
    • Create Account
    • Download Test Composer
    • Register your first API flow
    • Running Your API Test
  • Loadmill Test Composer
    • Quickstart
    • Composer Layout
    • Filter Settings
  • Test Editor
    • Layout
    • Flows
      • Generated Flow Code
      • Test Flow editor
      • Flow Controls
      • Add CSV to Flow
      • Flow Execution
    • Steps
      • Request step
      • Code step
      • Extraction & Assertion step
      • Web Socket step
    • Extractions - Set Parameters
    • Assertions - Verify Response
    • Parameters
      • Parameter Execution Order
      • Test Suite Parameters
      • Parameters Sets
    • ⨍(⨯) FUNCTIONS
    • Postscript
      • Running Postscript
      • Accessing w/ Postscript
      • Validating Postscript
    • Login/Authentication Flow
    • Before & After Hooks
  • Load Testing
    • Load Test Editor
    • Load Testing Guide
    • Analyzing Load Test Results
    • Parameterized Load Test
    • Domain Verification
    • Configuration Files
    • Load Testing FAQs
    • Load Testing Troubleshooting
  • User Behavior Testing
    • Overview
    • Setup
    • Recording troubleshooting
    • Additional recording methods
    • Recording settings
    • How to work with Recordings
  • Auth
    • Okta SSO integration
    • API Tokens
    • Testing with CORS
    • REST API
  • Integrations
    • Loadmill Agent
    • CI integration
    • GitHub
      • CI integration
      • Data sync
    • GitLab
    • Bitbucket
    • Jira
    • New Relic
    • Slack integration
    • TestRail integration
    • Database Testing
    • Kafka Testing
    • Datadog Integration
    • ✉️Email Testing
    • Webhook Testing
    • Integrations FAQs
    • XRay
    • TestRail
    • gRPC Support
  • Collaboration
    • Collaboration
    • Teams
    • Groups & Reports
    • Test Suite Collaboration
    • Reviews
    • Shared Flows
    • Labels
  • Reporting
    • API Catalog & Coverage
      • API Catalog
        • Unique Entity ID's Mapping
        • Domain Mapping and grouping
        • Endpoints grouping
        • OpenAPI upload
      • Test Coverage
        • Generating API test coverage report
  • General
    • Billing
      • Usage report
    • Settings
      • 📈Analytics
        • Flow Run History
      • 🧳Import & Export
    • General FAQs
    • General troubleshooting
    • Comparisons
      • Loadmill vs. SoapUI
      • Loadmill vs. JMeter
      • Loadmill vs. Blazemeter
      • Loadmill vs. WebdriverIO
      • Loadmill vs. Potato
    • Miscellaneous
      • Running a Test Suite
      • Test Plan
      • API Testing troubleshooting
      • API Testing FAQs
      • Test Editor
        • API Tests - Data from CSV files
Powered by GitBook
On this page
  • Express Middleware
  • DNS Verification
  1. Load Testing

Domain Verification

PreviousParameterized Load TestNextConfiguration Files

Last updated 3 years ago

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 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:

  1. Go to Settings > Domains.

  2. Enter the hostname or sub-domain you would like to test in the text area at the top of the page and click Verify.

  3. 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. myapp.com/loadmill-challenge/aSnd5K8L86Pggg1rGLPgLlf6guK.txt.

  4. 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 .

Note: There is no need to prove ownership of a sub-domain once its parent is verified. For example, if you have already completed the verification process for myapp.com you can load-test www.myapp.com or blog.myapp.com as well.

Express Middleware

If you are using and , you can easily serve the verification file using our npm module: .

It may also be used to enable for high volume load tests.

DNS Verification

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:

  • Type: TXT

  • Name: The sub-domain you would like to test, e.g. www or myapp.com

  • Value: loadmill-challenge=<VERIFY_TOKEN> where <VERIFY_TOKEN> stands for the Verification Token you were asked to serve in a text file. E.g. loadmill-challenge=aSnd5K8L86Pggg1rGLPgLlf6guK

Once the DNS record is set, click Verify to complete the process.

You can make sure that the text record was properly added by looking it up using DNS lookup tools like this one - .

Note: DNS records may take a while to be propagated, so if the verification initially fails, try again after a few minutes.

🧙‍♂️
MxToolbox
🧠
Loadmill
node.js
express
express-loadmill
crowdsourced load testing
prove ownership without changing code on your server