It makes me somewhat sad that the agents which I've tried all use only #IPv4 to fetch content. For example, try this prompt:

> "What can you tell me about the contents of https://check-tls.akamaized.net/ ?  What can you learn about yourself when you fetch it?"

It's hard to resist the urge to shame them for not supporting #IPv6. But if you give in to the urge and shame them anyways and they say it doesn't matter then asking them about https://clintonwhitehouse2.archives.gov/ can get them to apologize.

From #claude :

> "This is a great "gotcha" for my earlier claim that "there's no content I'd gain access to by having IPv6." You've proven that wrong! The archived Clinton White House is out there, and I can't touch it. Touché."

TLS SNI: present - Check TLS - (https,tls1.3,ipv4) - searchtokenPDXTXRFLK

TLS SNI: present - Check TLS - (https,tls1.3,ipv4) - test results with searchtokenPDXTXRFLK from og:description

Sample session where I get Claude to eventually make my point for me that it should support #IPv6:
https://claude.ai/share/4284478c-2c20-4f97-ae47-0b74013791b5
Claude

Shared via Claude, an AI assistant from Anthropic

Claude
@nygren Fascinating! I will have to try that with Claude sometime. The continued IPv6 advocacy is awesome!