Bob's Multi Tool

DNS Lookup

dns lookupdns checkerdns records lookupdns deployment checkerPrivacy: Server route

DNS Lookup

Look up public DNS records, inspect A/AAAA, CNAME, MX, TXT, SPF, DMARC, and NS signals, and copy a deployment report.

Input / Output

Start with the tool

Input, output, and copy actions stay in this main surface. Examples and reference checks are separated below.

Copy-ready output

Local session

Input state is saved only in this browser so you can restore the last workspace without an account.

Review after the result

Open examples, checks, and related tools only after the primary input/output flow is done.

Web operations workbench

Check a DNS deployment

Verify records, HTTP reachability, sitemap exposure, and robots rules after a domain change.

3 Tools
  1. 1. DNS

    Check A, AAAA, CNAME, MX, TXT, and NS records, then copy the DNS report.

  2. 2. HTTP

    Confirm the public URL returns the expected status.

  3. 3. Sitemap

    Prepare clean sitemap URLs and copy the discovery report after routing is stable.

Debug a redirect

Check status, final URL, DNS target, and social preview signals in one path.

3 Tools
  1. 1. HTTP

    Follow the redirect chain and final response.

  2. 2. DNS

    Confirm apex, www, and CNAME records point where expected.

  3. 3. URL Parse

    Break down query parameters and canonical path changes.

Review security headers

Check response headers, draft a CSP, then confirm the URL and DNS target are the site you meant to protect.

3 Tools
  1. 1. HTTP

    Inspect status, redirects, pasted headers, and CSP warnings in one surface.

  2. 2. URL Parse

    Separate origin, path, query, and tracking parameters before writing policies.

  3. 3. DNS

    Confirm the hostname resolves to the deployment you are reviewing.

Before copying

  • Query the exact record type you need, such as A, CNAME, MX, TXT, or NS.
  • Compare apex and www records when debugging a public site.
  • Follow up with HTTP Status Checker after DNS resolves to the expected target.

Common failure cases

  • Public DNS resolvers can show cached records while a migration is still propagating.
  • Private, localhost, and reserved hosts are rejected to avoid internal network probing.

Related tools

HTTPCheck HTTP status, request-profile reachability, redirect diagnostics, final URL, response headers, pasted header blocks, CSP drafts, and a copyable public URL report.Next step: Inspect status codes and response headersURL ParseBreak URLs into protocol, host, pathname, query params, hash, origin, clean URL, and a canonical report.Next step: Inspect redirects, callback URLs, query parameters, duplicate canonical reasons, and copy a canonical review report.MIMELook up common MIME types by file extension or content type.Next step: Check headers and upload content types quickly.
  • Query the exact record type you need, such as A, CNAME, MX, TXT, or NS.
  • Compare apex and www records when debugging a public site.
  • Follow up with HTTP Status Checker after DNS resolves to the expected target.
DNS Lookup - Free Online Network Tool | bobob.app