DNS resolution, the encrypted connection and the HTTP response answer different questions. Use the reported layer to guide the next investigation.
- DNS resolution
- TLS connection
- HTTP response
How to use this tool
- Enter the public website hostname.
- Run the check to fetch its homepage and permitted redirects.
- Review the response status, final destination, title, description and available header observations.
Understanding the results
- Response and redirects
- A successful response confirms this request completed. Review unexpected redirects or error statuses before troubleshooting page content.
- Page metadata
- The tool reads title, description and other available signals from the returned HTML. Compare them with the page you intend visitors to see.
- HTTP headers
- Headers describe aspects of delivery and browser behavior. A missing header needs context before changing server settings.
What this check covers
This is a single fetch from Zevonix’s server, without executing the page’s JavaScript. A WAF, login requirement or bot restriction can limit the response. It is not an uptime monitor, full-site crawl or confirmation that Google has indexed the page.
Common questions
Does this check every page on my website?
No. It checks the public homepage for the entered hostname. Different pages can have different metadata, redirects and errors.
Why is a title visible in my browser but missing here?
Some sites insert metadata using JavaScript or return different HTML to automated requests. Inspect the original response and rendered page together.