[TLS] RFC 9460 HTTPS non-default port on the public Internet ? (attrleaf)

"Jesse Wilson" <[email protected]> Sun, 26 Jul 2026 10:58:34 -0400
Newsgroups	gmane.ietf.tls
Message-ID	<[email protected]>
--===============2545927182015866184==
Content-Type: multipart/alternative;
 boundary=703922555f75e090e411e6f795bd083552de37c0

--703922555f75e090e411e6f795bd083552de37c0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Yuri and I are working on SVCB + ECH stuff for OkHttp. We=E2=80=99ve got=
 the happy path working.

I=E2=80=99m currently looking for real-world, public Internet examples t=
o test interop. https://tls-ech.dev has been excellent here, particularl=
y because it exercises some failure modes.

I=E2=80=99m looking for an HTTPS site on a port other than 443 that has =
an HTTPS resource record. For example, the RFC includes a sample record =
for https://example.com:8443/:

```
_8443._https.example.com. IN HTTPS 1 alt3.example. (port=3D9443 alpn=3Dh=
2,h3 foo=3D... )
```

If you have a sample, please share!

I=E2=80=99d also be happy to skip it if it=E2=80=99s not used in practic=
e! I fetched the HTTPS records for a million domains on the default port=
 and found that most service parameters are very rarely used. The port s=
howed up only once <https://www.nslookup.io/domains/airnewzealand.co.nz/=
dns-records/https/>, and it was redundant.

Thanks!
=E2=80=93 Jesse

--703922555f75e090e411e6f795bd083552de37c0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>Yuri and I a=
re working on SVCB + ECH stuff for OkHttp. We=E2=80=99ve got the happy p=
ath working.</div><div><br></div><div>I=E2=80=99m currently looking for =
real-world, public Internet examples to test interop. <a href=3D"https:/=
/tls-ech.dev">https://tls-ech.dev</a> has been excellent here, particula=
rly because it exercises some failure modes.</div><div><br></div><div>I=E2=
=80=99m looking for an HTTPS site on a port other than 443 that has an H=
TTPS resource record. For example, the RFC includes a sample record for =
https://example.com:8443/:</div><div><br></div><div>```</div><div>_8443.=
_https.example.com. IN HTTPS 1 alt3.example. (port=3D9443 alpn=3Dh2,h3 f=
oo=3D... )</div><div>```</div><div><br></div><div>If you have a sample, =
please share!</div><div><br></div><div>I=E2=80=99d also be happy to skip=
 it if it=E2=80=99s not used in practice! I fetched the HTTPS records fo=
r a million domains on the default port and found that most service para=
meters are very rarely used. The port showed up <a href=3D"https://www.n=
slookup.io/domains/airnewzealand.co.nz/dns-records/https/">only once</a>=
, and it was redundant.</div><div><br></div><div>Thanks!</div><div>=E2=80=
=93 Jesse</div><div><br></div></body></html>
--703922555f75e090e411e6f795bd083552de37c0--


--===============2545927182015866184==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVExTIG1haWxp
bmcgbGlzdCAtLSB0bHNAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB0
bHMtbGVhdmVAaWV0Zi5vcmcK

--===============2545927182015866184==--