Website Inspector
Check public DNS, HTTPS, redirects, response headers, and basic page signals in one report.
A clearer view of your website
A focused overview of DNS, HTTPS, redirects, SEO signals, and security headers.
How to use Website Inspector
- Enter a public domain or an HTTP or HTTPS URL. Include the page path when you want to inspect a specific page.
- Select Inspect website to run server-side checks against the public target.
- Review the individual checks and their details. Use the DNS, SSL, or redirect tools to investigate a particular result.
What is Website Inspector?
Website Inspector brings together a first pass at the public website stack: name resolution, HTTPS and certificate dates, HTTP responses, redirects, selected security headers, page metadata, and the conventional robots.txt and sitemap.xml locations. Its score summarizes these checks; it is not a security certification, a full crawl, or a prediction of search rankings.
- Public DNS resolution and HTTP response checks
- Certificate date checks for HTTPS targets
- Redirect tracing and selected security-header checks
- Page title, meta description, canonical, and discovery-file checks
What the report measures
The checks examine the response received by ADEMN's server. Page metadata is read from returned HTML without running page JavaScript. A robots.txt or sitemap.xml availability check confirms that the standard URL responds; it does not validate every directive or prove that a page is indexed.
A detected security header is a configuration signal, not proof that its value is effective. Certificate dates describe the validity window and must be considered separately from hostname matching and certificate-chain trust. Review the details before drawing conclusions from a score.
Server-side checks and privacy
The submitted target is sent to ADEMN's server so it can resolve DNS and make public network requests. Reports are generated on demand and are not saved by the application. Your browser's cookies and Authorization header are not forwarded to the target.
Use public URLs without passwords, private access tokens, or signed query parameters. The target website receives the diagnostic request and may record it in its own access logs. Responses can differ from your browser because of location, caching, authentication, or bot protection.
A practical example
Illustrative input only: https://example.com/
Illustrative report layout, not a live result: DNS: public addresses HTTP: final response status HTTPS: certificate date window Page: title, description, canonical Discovery: robots.txt and sitemap.xml availability
Learn a little more
How to troubleshoot a DNS changeHow to check the certificate a website actually servesHow to diagnose redirect chains without losing the query stringFrequently asked questions
Does a high score mean my website is secure?
No. The score summarizes a small set of availability and configuration checks. It does not test application vulnerabilities, all TLS settings, header-policy effectiveness, or the full website.
Why does the report differ from what I see in my browser?
The request comes from ADEMN's server without your login session and without running page JavaScript. Regional routing, caching, bot protection, and client-side rendering can produce different responses.
Does the tool inspect every page?
No. It inspects the submitted URL and the final response reached through HTTP redirects, along with selected DNS, certificate, and discovery-file checks. It is not a site crawler.
Are my diagnostic reports saved?
The application does not persist reports. Your target is sent to the server to perform the check, and the target website may log the request. Avoid URLs containing credentials or private tokens.