Website & HTTP Diagnostics

When a site misbehaves, the evidence is in its certificate, its headers and the files crawlers read. These tools fetch a page the way a browser or a search engine would and show what came back: the certificate chain and TLS versions a host negotiates, the status and timing of a request, every hop of a redirect, the caching and compression headers, the canonical and Open Graph tags, and whether robots.txt, the sitemap, the favicon and the web manifest are where they should be and say what they should.

Checks run from the Mutqan server or, for the HTTP/2 and HTTP/3 and region checks, from the measurement network the page names, within strict limits on size, time and link depth. Each tool explains how to read the result and the cases it cannot see from outside — a login wall, a geo-blocked origin, a bot challenge — so a red mark is a finding, not a guess.

Tools in this category

Read the TLS certificate a server presents, or a pasted PEM: names, issuer, validity dates, days left, key, fingerprints and hostname match.

Website & HTTP Diagnostics

Test which TLS versions a server accepts, the cipher suite it negotiates, weak suites and HSTS, with an A+ to F grade that explains every cap.

Website & HTTP Diagnostics

Check the chain a server sends, or a pasted PEM bundle: order, missing intermediates, CA flags, dates, and whether each certificate is signed by the next.

Website & HTTP Diagnostics

Check whether a site serves HTTP/2, verified by a Globalping probe, and whether it advertises HTTP/3 in its Alt-Svc header.

Website & HTTP Diagnostics

Request a URL from Globalping probes in the regions or countries you choose and compare status codes and DNS, connect, TLS and first-byte times by location.

Website & HTTP Diagnostics

A one-time check of whether a website answers right now: one request from 3 to 5 Globalping probes worldwide, with each probe's status code and time.

Website & HTTP Diagnostics

Fetch or paste a robots.txt file, check it against RFC 9309 and test whether a crawler may fetch the paths you list.

Website & HTTP Diagnostics

Validate an XML sitemap or sitemap index against the sitemaps.org protocol: structure, URLs, lastmod dates, limits and hreflang alternates.

Website & HTTP Diagnostics

List every URL in an XML or text sitemap, filtered, de-duplicated and sorted by lastmod, as plain text or a CSV table.

Website & HTTP Diagnostics

Fetch a page and check its rel="canonical" link and Link header, the redirects before it, the canonical target and the hreflang set.

Website & HTTP Diagnostics

Read a page's Open Graph and Twitter/X card tags and see the title, description, image URL and site name a shared link would use.

Website & HTTP Diagnostics

List every link on a web page with its resolved URL, anchor text, rel values and internal or external type, as a table, a list or CSV.

Website & HTTP Diagnostics

Have the Mutqan server request the links of a web page and list which answer with an error, redirect or no answer at all.

Website & HTTP Diagnostics

See which CMS, frameworks, servers, CDNs and analytics a website shows signals of, with the header, cookie or script behind every match.

Website & HTTP Diagnostics

Audit a URL's redirect chain hop by hop: permanent or temporary, HTTPS upgrade, host changes, loops, slow hops, lost paths and meta refresh.

Website & HTTP Diagnostics

List the favicons, Apple touch icons and manifest link a page declares and check that each icon file answers with an image.

Website & HTTP Diagnostics

Find and validate a site's web app manifest, or a pasted one: members, start_url and scope, display mode, icons and install readiness.

Website & HTTP Diagnostics

Fetch a URL and see how browsers and CDNs may cache it: Cache-Control, lifetime, ETag and Last-Modified, Vary, Age and the CDN cache status.

Website & HTTP Diagnostics

Check whether a URL is served compressed with gzip or Brotli, compare the sizes reported for each encoding and the Vary header.

Website & HTTP Diagnostics

Also in this category

Validate Content-Type headers and check that a response body actually matches its declared media type.

Opens Content-Type Validator