--- title: Interesting: Bootstrapping HTTPS « ipSpace.net blog description: A brief pointer to Jan Schaumann's blog post exploring how browsers determine whether to use QUIC vs HTTPS over TCP. The post notes that while DNS HTTPS... canonical: https://daily.dev/posts/interesting-bootstrapping-https-ipspace-net-blog-4p0zpayoz twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Interesting: Bootstrapping HTTPS « ipSpace.net blog | daily.dev og:description: A brief pointer to Jan Schaumann's blog post exploring how browsers determine whether to use QUIC vs HTTPS over TCP. The post notes that while DNS HTTPS... og:url: https://daily.dev/posts/interesting-bootstrapping-https-ipspace-net-blog-4p0zpayoz og:image: https://api.daily.dev/og/posts/4P0ZPayOZ.png og:image:alt: Interesting: Bootstrapping HTTPS « ipSpace.net blog og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Interesting: Bootstrapping HTTPS « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 1 min read · 0 upvotes · 0 comments ## Summary A brief pointer to Jan Schaumann's blog post exploring how browsers determine whether to use QUIC vs HTTPS over TCP. The post notes that while DNS HTTPS records (RFC 9460) exist to advertise server capabilities, browser vendors don't fully trust this data and instead use a happy eyeballs-like negotiation protocol to choose between HTTPS over TCP and QUIC. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why don't browsers just use DNS HTTPS records to decide whether to use QUIC? Browser vendors don't fully trust DNS HTTPS records (RFC 9460), which are designed to advertise server capabilities like QUIC support. Instead, they implement a happy eyeballs-like protocol that races or negotiates between HTTPS over TCP and QUIC at connection time, rather than relying solely on what the DNS record advertises. _Developers navigating HTTP/3 and QUIC deployment decisions track protocol developments like this on daily.dev._ ## Similar posts on daily.dev - [savearoundtrip](https://daily.dev/posts/savearoundtrip-ya2ennr2i) · Lobsters · 0 upvotes · 0 comments - [EP200: HTTP/2 over TCP vs HTTP/3 over QUIC](https://daily.dev/posts/ep200-http-2-over-tcp-vs-http-3-over-quic-o83jfjirb) · ByteByteGo · 10 upvotes · 0 comments - [HTTP/2 and HTTP/3: what changed and why it matters](https://daily.dev/posts/http-2-and-http-3-what-changed-and-why-it-matters-kxd7rny7x) · Flavio Copes · 1 upvotes · 0 comments --- Tags: [#networking](https://daily.dev/tags/networking), [#dns](https://daily.dev/tags/dns) [View this post on daily.dev](https://daily.dev/posts/interesting-bootstrapping-https-ipspace-net-blog-4p0zpayoz) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Interesting: Bootstrapping HTTPS « ipSpace.net blog","url":"https://daily.dev/posts/interesting-bootstrapping-https-ipspace-net-blog-4p0zpayoz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/interesting-bootstrapping-https-ipspace-net-blog-4p0zpayoz"},"datePublished":"2026-08-11T08:52:05.123Z","dateModified":"2026-08-11T08:55:27.462Z","description":"A brief pointer to Jan Schaumann's blog post exploring how browsers determine whether to use QUIC vs HTTPS over TCP. The post notes that while DNS HTTPS...","image":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","thumbnailUrl":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/interesting-bootstrapping-https-ipspace-net-blog-4p0zpayoz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"networking,dns","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"Interesting: Bootstrapping HTTPS « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/interesting-bootstrapping-https-ipspace-net-blog-4p0zpayoz#faq","mainEntity":[{"@type":"Question","name":"Why don't browsers just use DNS HTTPS records to decide whether to use QUIC?","acceptedAnswer":{"@type":"Answer","text":"Browser vendors don't fully trust DNS HTTPS records (RFC 9460), which are designed to advertise server capabilities like QUIC support. Instead, they implement a happy eyeballs-like protocol that races or negotiates between HTTPS over TCP and QUIC at connection time, rather than relying solely on what the DNS record advertises. Developers navigating HTTP/3 and QUIC deployment decisions track protocol developments like this on daily.dev."}}]} ```