Why use the backend instead of browser DNS?

The backend queries many global resolvers in parallel from server-side DoH, giving a propagation view a single browser resolver cannot provide.

Which record types are supported?

A, AAAA, MX, TXT, NS, CNAME, and SOA.

Compare DNS answers from global public resolvers in one request

Server-side DoH queries — no browser consent banner needed.

Try an example:

Query multiple public DNS resolvers in parallel and see whether your DNS change has propagated worldwide.

Define mock REST routes and intercept fetch calls client-side

Estimate how long a file takes to transfer at a given connection speed — correctly handling bits vs bytes (Mbps vs MB/s) and SI vs binary size units

Extract http(s) links from pasted HTML and check them via proxy

Convert cURL commands to code snippets in multiple languages. Parse cURL and generate JavaScript, Python, PHP, and more.

Query DNS records and resolve domain names to IP addresses

Parse email message headers to trace routing and authentication