If your content is served over HTTP/3, make sure your DNS record advertises it, otherwise you're missing out on free performance.

Check your site here: https://savearoundtrip.com/

savearoundtrip

Publish an HTTPS DNS record. Let browsers reach HTTP/3 on the first connection instead of wasting a round trip.

@firefoxwebdevs thanks a lot !
Must act on my domain now
@firefoxwebdevs Or use the #DNS yourself, may be through a fediverse gateway: https://mastodon.gougere.fr/@DNSresolver/116754611721915909
DNS resolver bot (@[email protected])

@bortzmeyer 1 . alpn="h3,h2" ipv4hint="188.114.96.2,188.114.97.2" ech="AEX+DQBBNAAgACBj0iSjcad409RCAxZK3Opr0uknrmXVW7aEyA4QEjLTKQAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA=" ipv6hint="2a06:98c1:3120::2,2a06:98c1:3121::2"

Mastodon - Gougère Network
@firefoxwebdevs already doing it 🙂
@firefoxwebdevs how come I didn't get served the content on http3 on the play store version of Firefox then? What requirements am I failing to meet? Do I need dns-over-https for this to function?
@vivithecanine @firefoxwebdevs savearoundtrip.com author here. You do not need DoH. Firefox can resolve HTTPS RR on most OSs via their native resolvers, too. Would you mind trying the Firefox Nightly Android app? If that doesn't work, let's discuss / debug on https://bugzilla.mozilla.org/. Thank you!
Bugzilla Main Page