$ curl -i 'https://xn--971h.com' curl: (6) Could not resolve host: xn--971h.com

yreg · on July 24, 2023

    $ curl 𝕏.com
    <html>
    <head><title>400 Bad Request</title></head>
    <body>
    <center><h1>400 Bad Request</h1></center>
    <hr><center>cloudflare</center>
    </body>
    </html>

ricardo81 · on July 24, 2023

What's that all about then? I'd expect curl to deal with either/or

curl should especially live with a punycode version.

Unless the punycode from the OP is incorrect? From basic online tools, it looks like it simply converts to x.com

jrockway · on July 24, 2023

I get:

  $ curl http://𝕏.com -v
  *   Trying 34.102.136.180:80...
  * Connected to 𝕏.com (34.102.136.180) port 80 (#0)
  > GET / HTTP/1.1
  > Host: x.com
  > User-Agent: curl/8.1.2
  > Accept: */*
  >
  < HTTP/1.1 200 OK

No https, though. (OpenSSL SSL_connect: Connection reset by peer in connection to x.com:443)