Check how a domain resolves through an encrypted DNS connection using our DNS over HTTPS Test. Enter a domain name, choose a DNS record type, and query Cloudflare or Google Public DNS to view the response.
The tool displays DNS records, response status, Time to Live (TTL), and server-side request time. It is useful for checking DNS configuration, investigating resolution problems, and comparing results from different public DNS resolvers.
Look up a public domain through an HTTPS-encrypted DNS resolver and inspect the returned DNS records. This lookup runs from the website server, not your browser or home network. It cannot determine whether DoH is enabled on your device. The website server sends a standard RFC 8484 DNS query over HTTPS to your selected resolver. Results show the DNS response status, records (when available), and time measured on the website server for the HTTPS request. What it does not check: your browser's default DNS settings, your ISP's DNS configuration, general internet speed, or DNSSEC validity. A successful lookup only confirms this particular resolver request worked from the website server. Privacy: the domain you enter is sent to this website's server and then to the resolver you select. This plugin does not save query histories in the WordPress database, but hosting systems and DNS providers may keep their own logs. Avoid entering confidential internal hostnames.DNS over HTTPS Test
What this test checks
How to Use the DNS over HTTPS Test
- Enter a domain name. Type a public domain such as
example.com. Do not includehttps://, a URL path, or a port number. - Select a DNS record type. Choose A, AAAA, MX, TXT, CNAME, NS, SOA, CAA, or PTR.
- Choose a DNS resolver. Select Cloudflare or Google Public DNS.
- Run the lookup. Click the Run DNS over HTTPS Lookup button.
- Review the results. Check the DNS response status, returned records, TTL values, and server request time.
You can repeat the lookup using the other resolver to compare answers.
What Is DNS over HTTPS?
DNS over HTTPS (DoH) is a protocol that sends Domain Name System (DNS) queries and responses over an encrypted HTTPS connection.
DNS translates domain names into information that computers use to locate websites, mail servers, and other internet services. For example, an A record associates a domain name with an IPv4 address.
Traditional DNS queries can travel without encryption. DoH protects the DNS query and response in transit between the DoH client and the selected resolver using HTTPS.
DoH is defined in RFC 8484. It improves DNS transport confidentiality, but it does not make internet activity anonymous. The selected resolver can still process the domain names submitted to it.
Supported DNS Record Types
Our DNS over HTTPS lookup supports nine common DNS record types.
| Record | What It Shows |
|---|---|
| A | IPv4 addresses associated with a domain |
| AAAA | IPv6 addresses associated with a domain |
| MX | Mail exchange servers and their priorities |
| NS | Nameserver records for a domain |
| TXT | Text records, including those used for domain verification and email authentication |
| CNAME | Canonical-name aliases pointing to another hostname |
| SOA | Start of Authority information for a DNS zone |
| CAA | Certificate authorities authorized by a domain’s CAA policy |
| PTR | Hostname information from reverse DNS records |
For PTR lookups, enter a reverse DNS name rather than a raw IP address. For example, to query the reverse record for 8.8.8.8, enter 8.8.8.8.in-addr.arpa.
Not every domain has every type of DNS record. An empty answer for one record type does not necessarily indicate a configuration problem.
How to Understand Your DNS Test Results
DNS Response Status
The response status indicates how the resolver handled the DNS query.
- NOERROR: The query was processed successfully. It does not necessarily mean a matching record exists.
- NXDOMAIN: The resolver reports that the requested DNS name does not exist.
- SERVFAIL: The resolver could not complete the DNS resolution.
- REFUSED: The resolver declined to process the query.
- FORMERR: The resolver reported a DNS message format error.
A NOERROR response with no answer records can be normal. For example, a domain might have an A record but no AAAA record.
DNS Record Values
The returned records contain information associated with the requested domain.
For an A lookup, you may see one or more IPv4 addresses. An MX lookup can return mail servers and their priorities. TXT records may contain domain-verification or email-authentication information.
Some records can be long. The tool may shorten unusually long TXT values for display.
TTL (Time to Live)
TTL is displayed in seconds. It indicates how long a DNS response can remain cached before it must be refreshed, subject to resolver behavior and caching policies.
A low remaining TTL does not automatically mean a problem. It may simply indicate that a cached record is approaching expiry.
Server Request Time
The displayed time measures how long the NetTools Pakistan website server took to make the HTTPS request and receive a response from the selected resolver.
It is not your device’s DNS latency, internet download speed, or home network response time.
Cloudflare vs. Google Public DNS
The tool supports two public DNS providers:
Cloudflare DNS: A public recursive DNS resolver that supports DNS over HTTPS.
Google Public DNS: Google’s public recursive DNS service, which also supports the DNS over HTTPS standard.
You can compare their returned records by selecting each resolver in turn.
Results may differ because of DNS caching, recent DNS changes, geographic responses, or resolver-specific behavior. A difference does not necessarily mean either resolver is faulty.
For a domain that has recently changed hosting providers or nameservers, comparing the returned records can help identify inconsistent cached information.
Does This Test Check Whether DNS over HTTPS Is Enabled?
No. This is a DNS-over-HTTPS lookup tool, not a browser or network DoH detection test.
When you submit a domain, the request goes from your browser to the NetTools Pakistan website server. The website server then sends a DNS query over HTTPS to your selected public resolver.
A successful result confirms that the website server completed that particular DoH lookup. It does not prove that:
- Your browser is configured to use DoH.
- Your router or ISP uses encrypted DNS.
- All DNS queries from your device are encrypted.
- DNSSEC validation has succeeded.
- Your internet connection is faster or more secure overall.
To examine your own DoH configuration, you must check the relevant browser, operating system, or network settings.
Why Might a DNS Lookup Fail?
A failed request does not always mean the domain is offline.
Invalid domain name: Check spelling and enter a domain rather than a complete website URL.
NXDOMAIN: Confirm that the domain exists and that you entered the correct name.
SERVFAIL: Try the other DNS provider. If the error continues, examine the domain’s authoritative DNS configuration.
No records returned: Try another record type. The domain may not publish the selected record.
Resolver connection error: The website server may be unable to contact the provider, or the request may have timed out.
DNS resolution is only one part of website availability. A domain can resolve correctly even when its website or application server is unavailable.
Privacy and Security
DNS over HTTPS encrypts DNS requests between the website server and the chosen DoH resolver. When this page is served over HTTPS, the visitor-to-website connection is also encrypted.
The domain you submit is processed by the NetTools Pakistan website server and sent to Cloudflare or Google Public DNS, depending on your selection.
The tool plugin does not create a separate WordPress database history of lookups. However, website hosting systems, network services, and DNS providers may maintain their own logs.
Avoid submitting confidential internal hostnames or sensitive information.
NetTools Pakistan is an independent internet connectivity website and is not affiliated with Cloudflare, Google, PTCL, or the Pakistan Telecommunication Authority.
When Should You Use a DNS over HTTPS Lookup?
This tool is useful when you need to inspect a domain’s DNS records, compare public resolver responses, check mail-related DNS entries, or investigate whether recent DNS changes appear in resolver answers.
For example, after moving a Pakistani business website to another hosting provider, you can query its A, AAAA, or NS records and compare the returned information with the settings supplied by your hosting provider.
If the results remain unexpected, verify the authoritative DNS records with your domain or hosting provider. A single lookup cannot establish that changes have reached every resolver worldwide.
Technical References
- RFC 8484: DNS Queries over HTTPS
- Cloudflare DNS over HTTPS Documentation
- Google Public DNS over HTTPS Documentation