Start with the symptom
A browser failing to load a page does not identify the failing layer. The name might not resolve, the server might refuse a connection, TLS might fail, or the application might return an error. This site focuses on the first part: DNS answers and public IP metadata.
Check the name and record type
Use DNS Lookup with the hostname that actually fails. The bare domain and its www hostname can have different records. Compare A and AAAA separately. A working IPv4 path does not prove that an IPv6 path works, and an empty AAAA response can be intentional.
For email, inspect MX records and any relevant TXT policy. DNS records alone do not prove that a mail server is accepting messages. Do not treat a DNS lookup as a delivery test.
Read differences in context
After changing a record, keep the previous TTL in mind. Different public resolvers can hold old and new answers simultaneously until caches expire. A lower TTL set after a change does not retroactively shorten every cached copy of the old record.
Record the queried name, type, response status, answers and timestamp. The JSON download includes these together, which makes a before-and-after report more useful than a screenshot of an address without context.
Inspect the resulting address
IP Check can provide approximate network ownership and location. Hosting ownership does not identify which tenant operates a website. Shared hosting and CDN addresses can serve many unrelated domains. A city label should not be interpreted as the website owner’s location.
Know when another tool is needed
If DNS looks correct but the page still fails, inspect the browser’s network error and test HTTP or TLS separately. This service does not send arbitrary web requests to user-supplied URLs and does not scan ports. That keeps its results focused and avoids implying it has tested layers it never contacted.
Missing reputation data stays unknown. You cannot derive a trustworthy cleanliness percentage from a country, ASN or the absence of one reported flag. Keep observations separate from conclusions when sharing a report.