Skip to content

Domain Analyzer

Inspect any domain: DNS, TLS, security headers, technology, structured data and AI crawler policy. Measured live, nothing estimated.

This tool contacts our server. A browser cannot resolve DNS or read another host's certificate, so the domain you enter is sent to our server for analysis. Our server then queries the domain itself, its registry (RDAP) and an IP geolocation service. The result is published as a public report page.

The domain analyzer inspects any public domain and reports what it actually serves:
DNS and mail records, the TLS certificate, response headers, homepage metadata, detected
technology, structured data, and its robots.txt crawl policy including named AI crawlers.

Every figure is measured live at the moment you run it. Nothing is estimated and no
third-party SEO API sits behind it.

What does it check?

Each report covers nine areas, and each one is an observation rather than a score:

  • Response โ€” HTTP status, scheme, time to first byte, page size and compression.
  • Technology โ€” platform, framework and analytics fingerprints found in the markup and headers.
  • Homepage metadata โ€” title, meta description, H1, canonical, Open Graph, heading and image counts.
  • TLS certificate โ€” issuer, validity window, days remaining and the hostnames it covers.
  • Security headers โ€” HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy.
  • DNS โ€” A and AAAA records, reverse DNS, name servers, MX and SPF.
  • robots.txt โ€” whether one exists, declared sitemaps, and blanket crawl rules.
  • AI crawler policy โ€” whether GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot and others are allowed or blocked.
  • Structured data โ€” the schema.org types published on the homepage.

Why does this tool contact the server?

The other tools on this site run entirely in your browser because they can: formatting
JSON or decoding a JWT needs no network access. This one is different by necessity. A browser
cannot resolve DNS records, complete a TLS handshake against another host, or fetch a
third-party robots.txt โ€” the same-origin policy forbids it. So the domain you enter is sent to
our server, which performs those lookups and returns the result.

Which third parties does the server contact?

Three, and only for the domain you asked about:

  • The domain itself โ€” its homepage, robots.txt, and a TLS handshake on port 443.
  • The domain registry, over RDAP โ€” this returns the registration and expiry dates. RDAP is the registries’ own successor to WHOIS, so the answer is authoritative rather than scraped.
  • An IP geolocation service โ€” to turn the resolved IP address into a hosting country and network operator. This lookup is made over plain HTTP on the free tier, and carries only the target’s public IP address.

Nothing about you is sent to any of them. They receive the domain or IP being analysed, not your address, and the site runs no analytics on tool pages.

That has a consequence worth stating plainly: the resulting report is a public page
at /website/<domain>/, and the domain you look up is stored. Only information
the domain already serves publicly to any visitor appears there. If you own a domain and want
its report removed, email us and it will be.

What this tool does not tell you

There is no traffic estimate, no authority score and no ranking data here, because none of
that can be measured by looking at a domain directly โ€” it can only be modelled, and a modelled
number presented without its method is worse than no number. What you get is the observable
truth about a domain at one moment in time.

Response time is a single measurement from one server in one location. Treat it as a rough
signal, not a benchmark. Technology detection reads public fingerprints, so a site behind a CDN
or rendering entirely server-side will show less than it actually runs.

How often are reports refreshed?

A report is re-analysed when someone looks the domain up again and the stored result has
aged past the refresh window. Until then the cached report is served, so repeat lookups are
instant and cost nothing.

Frequently asked questions

Is the domain I enter made public?

Yes. Each lookup creates a public report page at /website/<domain>/. It contains only information the domain already serves publicly to any visitor.

Does this tool send my data to third parties?

It sends the domain you entered to our server, and our server queries three things about that domain: the domain itself, its registry over RDAP for the registration dates, and an IP geolocation service for the hosting country. None of them receive anything about you.

Does this show traffic or domain authority?

No. Those figures cannot be measured by inspecting a domain, only modelled. This tool reports observations, not estimates.

Can I analyse a domain that is offline?

You can try. If it does not resolve or returns no readable response, the report says so rather than guessing.

Why can this tool not run in my browser like the others?

Browsers cannot resolve DNS, read another host TLS certificate, or fetch a third-party robots.txt. The same-origin policy blocks it, so the lookups have to happen server-side.

How do I get a report removed?

Email hello@quikconsolecom.net from an address at that domain and it will be taken down.

Contact: contact@quikconsolecom.net