You want to validate that a DNS-over-HTTPS endpoint responds with usable JSON DNS answers.
DoH Endpoint Check
Test a DNS-over-HTTPS endpoint with a live JSON DNS query.
Use DoH Endpoint Check to verify that a DNS-over-HTTPS endpoint is reachable, accepts the query you expect, and returns a usable DNS response for the domain or hostname and record type you enter.
Check the DoH endpoint before assuming the DNS record or resolver integration is the problem.
Endpoint result
https://dns.google/resolve
READY
Type Value TTL
Check Result Time
No answer records were returned for this query from the selected endpoint.
What this DoH Endpoint Check tool does
DoH Endpoint Check sends a live DNS-over-HTTPS JSON query to the endpoint URL you enter and shows the HTTP result, DNS response status, and returned answer records.
Use it to confirm whether a DoH resolver endpoint is reachable, whether it accepts your query format, and whether it returns the DNS data you expect for the selected hostname and type.
It does not prove that every client can use the endpoint. Browser CORS policy and application-specific request formats can still differ.
When to use this tool
A resolver integration is failing and you need to confirm the endpoint URL, hostname query, and returned DNS status.
You are comparing a public DoH resolver with a custom or provider-specific DoH endpoint.
A browser or application is expected to use DoH and you need to verify endpoint behavior before deeper debugging.
You want to see whether the endpoint returns answers, NXDOMAIN, SERVFAIL, or an HTTP-level failure.
You need a quick check before moving to record-specific DNS, propagation, or DNSSEC troubleshooting.
How to use DoH Endpoint Check
- Enter the DoH endpoint URL you want to test.
- Enter the hostname and choose the record type you want to query.
- Run the check to send a live JSON DNS query over HTTPS.
- Review the HTTP status, DNS status, returned answers, and timing.
- If the result fails or looks wrong, compare with DNS Lookup, propagation, or DNSSEC checks.
How to interpret DoH endpoint results
HTTP and DNS success
Likely meaning: The DoH endpoint returned an HTTP success response and a usable DNS answer.
Common causes: This usually means the endpoint URL is valid, reachable from the browser, and responded to the query normally.
Next action: Review the returned records and compare them with the DNS data you expected.
HTTP success, no DNS data
Likely meaning: The endpoint responded, but no answers were returned for the selected query.
Common causes: The queried name may exist without that record type, the record may be missing, or the endpoint may return an empty NOERROR response.
Next action: Check DNS Lookup for other record types, then verify the exact hostname and expected record type.
NXDOMAIN
Likely meaning: The DoH resolver says the queried hostname does not exist.
Common causes: Typos, wrong subdomains, unpublished names, or the wrong zone are common causes.
Next action: Verify the exact hostname, then compare with another public resolver or DNS Lookup.
SERVFAIL
Likely meaning: The DoH resolver could not complete the lookup successfully.
Common causes: DNSSEC problems, broken delegation, or upstream authority issues commonly cause this.
Next action: Run DNSSEC Check and NS Lookup next, then compare results with another resolver.
HTTP failure or CORS block
Likely meaning: The browser could not complete the DoH request or the endpoint rejected the request.
Common causes: The endpoint may not support browser CORS, may require a different path, may be blocked, or may not implement JSON DoH queries on this URL.
Next action: Confirm the endpoint path, check whether browser access is allowed, and compare with a known public DoH endpoint.
Common issues this tool helps uncover
Wrong DoH path or incomplete endpoint URL
Endpoint does not allow browser CORS requests
Resolver returns empty answers for the selected record type
Custom DoH endpoint differs from public resolver behavior
HTTP success with DNS SERVFAIL because of DNSSEC or delegation problems
The query name is wrong even though the endpoint itself is healthy
Application behavior differs because the browser cannot access the same endpoint path
Next steps after DoH Endpoint Check
Compare with DNS Lookup
If the DoH endpoint answers unexpectedly, compare the same name and record type with a known public resolver.
Check propagation
If the endpoint returns stale-looking data, compare resolver views and cache differences.
Validate DNSSEC
If the DoH response shows SERVFAIL, DNSSEC validation issues may be involved.
Verify nameservers
If a custom DoH endpoint returns unexpected answers, confirm the underlying DNS delegation first.
Related tools
DNS Lookup
Query A, AAAA, CNAME, TXT, and other DNS records for a domain.
DNS Propagation Check
Verify whether recent DNS changes are visible across resolvers.
DNSSEC Check
Validate whether a domain has DNSSEC configured correctly.
NS Lookup
Check authoritative name servers and delegation for a domain.
HTTPS Check
Verify HTTPS availability, response chain, and TLS handshake basics.
DoH Endpoint Check FAQ
What does DoH Endpoint Check test?
It sends a live JSON DNS-over-HTTPS query to the endpoint URL you provide and shows the HTTP response status, DNS status, and returned answers.
What kind of endpoint should I enter?
Enter a DoH JSON endpoint URL such as https://dns.google/resolve. The page appends the query name and record type as URL parameters.
Why can a DoH endpoint fail in the browser even if it works elsewhere?
Some endpoints do not allow browser CORS requests or expect a different path or request format than the JSON query used here.
What should I query with this tool?
Use a hostname you expect to resolve, such as example.com or www.example.com, and select the record type you want to inspect.
What should I check after a DoH failure?
Confirm the endpoint URL, compare with DNS Lookup, and then move to DNSSEC or nameserver checks if the DNS status shows SERVFAIL.