Skip to main content
Back to Dev generators

Dev

Fake Domain & URL Generator

Hardcoding example.com into every test fixture tests only a single URL shape. Real applications encounter varied TLD lengths, path depths, and query strings — all of which trigger different parsing or truncation behavior. A fake domain and URL generator produces believable, varied web addresses across four URL types without routing to any live site. Three inputs control the output. Count sets the batch size (1–50). URL Type determines the structure: domain returns just the host, full returns a multi-segment page path up to three levels deep, api returns versioned REST endpoint paths (e.g., /api/v2/orders/4721), and image returns CDN-style asset URLs with dimension query parameters. TLD Preference pins to .com, .io, or .dev, or uses mixed mode to rotate across six TLDs. Do not use generated URLs in production code that makes real HTTP requests — domains could be registered at any time.

Read the complete guide — 4 min read

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Set the Count field to the number of URLs your test fixture or seed file requires.
  2. Choose a URL Type: pick 'full' for a mixed batch, or select domain, API endpoint, or image URL specifically.
  3. Select a TLD Preference — use 'mixed' for variety or pin to a specific extension like .io or .com.
  4. Click Generate to produce the list, then copy all results with the copy button.
  5. Paste the output directly into your seed script, fixture JSON, design file, or documentation.

Use Cases

  • •Seeding a PostgreSQL users table with varied website URLs across .com, .io, and country-code TLDs
  • •Writing Jest fixtures that test a URL parser against page paths, REST endpoints, and image asset URLs
  • •Filling Figma wireframe link fields with readable, pronounceable domains instead of example.com placeholders
  • •Generating versioned REST endpoint examples like /api/v2/orders/99 for internal API documentation
  • •Building phishing-simulation slides for security awareness training with realistic but non-functional URLs

Tips

  • →Use 'mixed' TLD mode when testing a URL-display component — short TLDs like .io and long ones like .museum expose truncation bugs.
  • →Generate API endpoint URLs specifically when building mock server configs; the versioned paths (/api/v2/...) map directly to common route patterns.
  • →For Figma mockups, generate 20+ URLs and paste into a bulk-rename or data plugin so every link field gets a unique value, not the same string repeated.
  • →Combine image asset URLs with a placeholder image service by stripping the fake domain and prepending a real CDN — you keep the realistic path and query string.
  • →If your parser must handle subdomains, manually prepend 'www.' or 'api.' to a few generated domains to add that variation to your fixture set.
  • →Run two batches with different TLD settings and merge them when you need a dataset that includes both familiar (.com) and less-common (.co, .io) extensions.

FAQ

are fake generated URLs safe to use in demos and internal docs

Yes — the domains are invented and the URLs resolve nowhere, so they are safe placeholders for demos, internal docs, mockups, and test fixtures. Do not make real HTTP requests to generated URLs in production code — domains could be registered by someone at any time.

why not just use example.com for every test URL

Repeating one domain tests only a single URL shape. Real applications encounter varied TLD lengths, path depths, and query strings — all of which can trigger different parsing or truncation behavior. A batch of mixed fake URLs surfaces edge cases that example.com never will.

what is the difference between the four URL types this generator produces

Domain returns just the host name (e.g., swiftforge.io). Full returns an https URL with a random 1–3 segment page path. API returns a versioned REST path like /api/v2/users/4721, optionally with a resource ID. Image returns an asset URL with width and height query parameters mimicking a CDN.

can I control the TLD of generated domains

Yes. TLD Preference lets you pin to .com, .io, or .dev, or use mixed mode to rotate across .com, .io, .dev, .net, .co, and .app. Pinning is useful when testing a parser with TLD-specific logic; mixed mode is better for variety in a seed dataset or fixture file.

You might also like

Popular tools from other categories that share themes with this one.

Numbers
Random Test SSN Format Generator
Generates fake SSN-format numbers for testing and development purposes only
Names
Fake Full Name Generator
Generates realistic fake full names with first name, last name, and optional middle name
Text
Placeholder Form Data Generator
Generates realistic fake form field content for names, emails, addresses, and bios

Try these next

More free tools from other corners of the catalog, picked by shared themes.

Colors
Random Color with HEX and RGB Generator
Generates a random color and displays it with HEX, RGB, and HSL values
Science
Random Coordinates Generator
Generates random latitude and longitude pairs for maps, testing, and games
Business
Random Currency Generator
Picks a random world currency with its ISO code and symbol