We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Check domain DNS records and HTTP status codes online to quickly diagnose website connectivity and network issues.
Enter a domain and click 'Check' to see results.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Enter one domain to request DNS answers and check how its HTTPS address responds. The DNS panel can show A and AAAA address records, CNAME aliases, MX mail exchangers, NS name servers, TXT text, SOA zone information, PTR pointers, CAA certificate-authority authorization, and SRV service records. A type appears when the lookup returns data. A DNS resolver answers queries using the DNS records available along its resolution path; this is a snapshot from that path, not a global propagation report.
The web response panel reports the HTTPS request's status code, final URL after redirects, and selected response headers. HTTP status codes describe a server response; a single response does not establish overall uptime, domain ownership, certificate validity, or security posture.
DNS records serve different purposes: A and AAAA map a name to IPv4 or IPv6 addresses; MX points toward mail handling; NS identifies authoritative name servers; TXT stores text data used by multiple protocols. CAA, SOA, PTR, SRV, and CNAME provide other kinds of DNS information. The tool displays records rather than explaining whether a particular configuration is correct for your provider.
The HTTPS check begins with the domain's HTTPS address and follows redirects. It uses a HEAD request and may retry with GET if the server rejects that method. Only selected headers are shown, so the result is not a complete response capture. A 2xx status indicates a successful response class, 3xx a redirection, 4xx a client error, and 5xx a server error; investigate the final URL and context before drawing conclusions.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter a hostname such as example.com. A full HTTPS URL can also be entered; the lookup uses its hostname.
Select Check and wait for the DNS and HTTPS results. Either panel may succeed while the other reports an error.
Review the DNS record types that returned values, then check the HTTPS status code, final URL, and visible headers.
If you need to investigate further, compare with the domain's DNS provider or hosting platform and repeat through a resolver or network relevant to the affected users.
For example, an A answer lists IPv4 address data; an MX answer lists mail exchanger data and priority. A missing type in this result means the lookup did not return that type here, not that the name is unregistered.
Use cases
See how the tool fits into real work and everyday tasks.
A site administrator can inspect returned address, alias, or name-server records and compare them with the values expected from the DNS provider. Differences may reflect resolver path or timing.
A developer reviewing a deployment can see the final HTTPS URL, status, and selected headers. A 3xx result helps reveal that the request was redirected, while a 4xx or 5xx calls for follow-up in the site logs or hosting console.
Q&A
Find concise answers to common questions and confusing cases.
No. It looks up DNS records and checks an HTTPS response. It does not provide WHOIS or registrar data.
No. A missing answer for one queried record type does not establish registration availability or prove that no other DNS data exists. Check the relevant registrar and authoritative DNS settings.
No. The result includes an HTTPS response status and selected headers, but this is not a certificate inspection or TLS configuration report.
Resolvers and network locations can see different answers because of delegation, cached data, and DNS changes in progress. Compare the resolver context and authoritative records before treating a difference as an error.
No. It does not test vulnerabilities, malware, email authentication quality, or the full security configuration of a site.
Notes
Review scope, result limitations, and important precautions before use.
Results are a one-time check from the resolver and network path used for the request. DNS responses can differ by resolver, location, delegation, and timing. An empty record panel or request error is not conclusive proof that a domain or service does not exist. The HTTPS check is not a global availability monitor, WHOIS lookup, certificate or TLS audit, or security assessment. Use it only for domains you are authorized to examine, and verify consequential changes with the domain owner, DNS operator, or hosting provider.
Related
Discover related tools, collections, and available API capabilities.