$ curl -v "https://node1.delegate.ipfs.io/api/v0/refs?recursive=false&arg=QmTJAaEpzLXgtpYadmX92xVYYLckL9t1GMUpdPAwVgqwb4&stream-channels=true"
[...]
* Server certificate:
* subject: CN=*.prod.dwebops.net
* start date: Mar 23 19:32:59 2020 GMT
* expire date: Jun 21 19:32:59 2020 GMT
* subjectAltName does not match node1.delegate.ipfs.io
* SSL: no alternative certificate subject name matches target host name 'node1.delegate.ipfs.io'
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, close notify (256):
curl: (60) SSL: no alternative certificate subject name matches target host name 'node1.delegate.ipfs.io'
As seen above, CN=*.prod.dwebops.net does not match *.delegate.ipfs.io nor *.preload.ipfs.io (AFAIK it should list both, as the same servers are acting as preload and delegate nodes)
I see the same problem as https://github.com/ipfs/infra/issues/498 on delegate nodes used in Brave when embedded js-ipfs is used:
As seen above,
CN=*.prod.dwebops.net
does not match*.delegate.ipfs.io
nor*.preload.ipfs.io
(AFAIK it should list both, as the same servers are acting as preload and delegate nodes)