How to force IPv4 or IPv6 connections in cURL

Forcing IPv4 or IPv6 connections with curl helps validate dual-stack deployments, compare performance between address families, and isolate routing or firewall issues. Restricting traffic to a single IP version exposes asymmetric paths and confirms that upstream services behave correctly when one family is preferred or required.

The curl client relies on the system resolver to translate hostnames into IP addresses and normally attempts connections in the order addresses are returned. Options such as --ipv4 and --ipv6 instruct curl to restrict connections to a specific address family, while HTTP semantics such as methods, headers, and payloads remain unchanged. Verbose and structured output options make it possible to see exactly which address was selected and how the handshake proceeded.

Using a single address family can reveal gaps such as missing AAAA records, broken IPv6 routing, or middleboxes that only handle IPv4. Some networks or servers offer no IPv6 support, so forcing --ipv6 can result in timeouts or resolution errors. When embedding these options into scripts, handling failures cleanly and providing fallbacks avoids unexpected outages when only one family is guaranteed to work.

1. Request the current public address without forcing any IP version to observe the default behavior.

   $ curl https://ifconfig.co
   203.0.113.24

   ifconfig.co echoes the source IP address that reaches the service and typically returns either a dotted-quad IPv4 address or a colon-separated IPv6 address.

2. Force IPv4 connectivity by adding --ipv4 to the request.

   $ curl --ipv4 https://ifconfig.co
   203.0.113.24

   The --ipv4 option restricts connections to IPv4 addresses even when DNS also supplies IPv6 records.

3. Force IPv6 connectivity by adding --ipv6 to the request.

   $ curl --ipv6 https://ifconfig.co
   2001:db8:abcd::24

   Forcing IPv6 with --ipv6 fails when the local network, router, or remote host lacks working IPv6 connectivity, which usually produces connection timeouts or name resolution errors.

4. Inspect the chosen address family and handshake details using verbose output.

   $ curl --ipv4 --verbose https://example.com/
   *   Trying 93.184.216.34:443...
   * Connected to example.com (93.184.216.34) port 443 (#0)
   ##### snipped #####

   The line starting with Connected to shows the remote IP address, confirming whether IPv4 or IPv6 was selected.

5. Verify the selected address family programmatically by printing only the remote IP address.

   $ curl --silent --output /dev/null --write-out '%{remote_ip}\n' --ipv4 https://example.com/
   93.184.216.34
   $ curl --silent --output /dev/null --write-out '%{remote_ip}\n' --ipv6 https://example.com/
   2001:db8:abcd::34

   Success signals: the IPv4 command prints a dotted-quad address, the IPv6 command prints a colon-separated address, and both commands exit with status code zero.