Request Path Simulator

Simulate the complete request path a URL takes from initial input through DNS resolution, hosting provider configuration, service-level redirects, and HTTP redirects. Import DNS records in BIND or JSON format, and see a detailed visualization of every step in the request journey. Perfect for verifying DNS configurations, understanding redirect chains, and debugging domain setup issues before deploying changes.

DNS Records

Drag and drop or

0 records
NameTypeTTLDataPriorityActions
No DNS records found. Click "Add Record" to create one.

Service Configuration

Configure how your hosting service handles domain aliases and redirects. This simulates service-level redirects (e.g., www → primary domain) that happen at the hosting provider level, separate from DNS. When DNS records are imported, the configuration is automatically detected. If a www subdomain is found, it will automatically redirect to the primary domain.

Domain Aliases

DomainTargetPrimaryRedirects ToActions
No domain aliases. Click "Add Alias" to create one.

Redirect Rules

FromToTypeActions
No redirect rules. Click "Add Redirect" to create one.

Target shows where each domain points, for example jsonyaml.com → Netlify.

Redirects to means this domain forwards to another one, like www.jsonyaml.comjsonyaml.com.

Redirect rules are extra HTTP rules (such as /old/*/new/*) that run after the domain is chosen.

Full DNS shows the complete simulated request path. curl modes approximate what a basic curl command would see.

Enter a URL and add DNS records to start simulation

Frequently Asked Questions

How does the request path simulator work?

Enter a URL and import your DNS zone file (BIND or JSON format). The tool will simulate the complete request path: DNS resolution with CNAME chains, hosting provider detection and configuration, service-level redirects (like www to primary domain), HTTP redirects, and the final destination.

What DNS formats are supported?

The tool supports BIND format zone files (commonly exported from DNS providers like Cloudflare) and JSON format DNS exports. You can upload a file or paste the DNS zone data directly.

Which hosting providers are detected?

The tool automatically detects and simulates configurations for Netlify, Vercel, Cloudflare Pages, AWS CloudFront, and generic hosting providers. It shows primary domain setup, domain aliases, and redirect rules.

What information does the simulation show?

The simulation shows: DNS resolution steps with CNAME chains, hosting provider configuration, service-level redirects, HTTP redirect chains, final destination, and detailed information for each step including timing and status codes.

Can I use this to test DNS changes before deploying?

Yes! Import your DNS zone file and test different URLs to see how requests would be handled. This helps verify configurations before making changes to production DNS records.