IPv4/IPv6 Support Checker

View an HTTP response summary before separate A and AAAA checks.

Target Evaluated:

-

200 OK Latency: - Redirects: 0

Final Destination URL: -

HeaderValue
No headers to display.

How to use it

  1. Enter the domain or URL whose web response you want to inspect.
  2. Select Check to make the implemented header request.
  3. Confirm Target Evaluated and the final destination.
  4. Review status, latency, redirects, and headers as HTTP context.
  5. Use Copy Result before running separate A and AAAA lookups.

The implementation does not resolve A or AAAA records and does not identify the connection address family. No dual-stack verdict is generated.

What is the purpose of the tool

IPv4/IPv6 Support Checker currently supplies a final HTTP response summary for a submitted address. That report can provide web endpoint context before a network protocol review.

The page does not test IPv4 and IPv6 separately. Dedicated A, AAAA, and reachability checks are required for dual-stack confirmation.

What parameters it generates in output

FieldMeaningHealthy result
Target EvaluatedThe normalized URL requested.It matches the intended site.
Status badgeThe final HTTP code and label.It is expected, but does not prove dual stack.
LatencyTotal header-request time.Use it only as HTTP context.
RedirectsThe count of followed redirects.The route is intentional.
Final Destination URLThe effective URL reached.It identifies the endpoint reviewed.
HeaderA final response header name.Required HTTP fields appear.
ValueThe content for that header.It matches the server configuration.

FAQs related to that specific tool

Does this checker request A and AAAA records?

No. Its code performs an HTTP header request and contains no DNS query for either record type.

Where is the IPv4 support result?

There is no IPv4 field or verdict in the visible output.

Where is the IPv6 support result?

There is no IPv6 address, reachability test, or status field.

Can an HTTP 200 prove dual-stack support?

No. A successful request may use one address family and does not establish that both work.

Does the backend port check reveal address family?

No. The hidden port_443_open Boolean does not identify whether IPv4 or IPv6 was used.

Can the browser fallback confirm either protocol?

No. It creates synthetic status and headers without exposing the connection address family.