Help
RSS
API
Feed
Maltego
Contact
Domain > tls-size-experiment-c.cloudflareresearch.com
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2025-06-14
162.159.135.79
(
ClassC
)
Port 80
HTTP/1.1 200 OKDate: Fri, 06 Dec 2024 20:20:33 GMTContent-Type: text/html;charsetUTF-8Content-Length: 2589Connection: keep-aliveAccess-Control-Allow-Origin: *Cache-Control: no-cache, no-store, must-re !doctype html> html> head> title>TLS handshake size experiment/title> style typetext/css> body { font-family: system-ui,-apple-system,Segoe UI,Roboto,Ubuntu,Cantarell,Noto Sans,sans-serif,BlinkMacSystemFont,Segoe UI,Helvetica,Arial,sans-serif,Apple Color Emoji,Segoe UI Emoji,Segoe UI Symbol; margin: 0; color: #1c1e21; } h1 { font-size: 2rem; line-height: normal; } a { color: #f38020; text-decoration: none; } #content { grid-area: content; margin-left: 2rem; margin-right: 3rem; line-height: 1.5rem; z-index: -5; max-width: 800px; } /style> body>article idcontent> h1>Cloudflare Research: TLS handshake size experiment/h1> p> On a small fraction of our challenge pages, weve been running an experiment to measure the performance impact of a larger TLS handshake. We were performing these measurements to understand the trade-offs involved when switching to post-quantum secure ciphers and signature schemes. /p> h2>What was the experiment?/h2> p> For challenge pages that are part of the experiment, we launched two background connections. On these background connections, we disabled certificate compression and added one or more dummy certificates to the server certificate chain to increase the size of the TLS handshake. These changes do not impact the security of the connection. /p> h2>Read about the results/h2> We a hrefhttps://blog.cloudflare.com/sizing-up-post-quantum-signatures/>published results on our blog/a>. h2>Contact/h2> p> You can reach us directly at a hrefmailto:ask-research@cloudflare.com>ask-research@cloudflare.com/a> with questions and fe
Port 443
HTTP/1.1 200 OKAccess-Control-Allow-Origin: *Cache-Control: no-cache, no-store, must-revalidateCf-As-Number: 16509Cf-Ray: 8edefa2e504fef7b-PDXContent-Type: text/html;charsetUTF-8Expires: 0Nel: {succes !doctype html> html> head> title>TLS handshake size experiment/title> style typetext/css> body { font-family: system-ui,-apple-system,Segoe UI,Roboto,Ubuntu,Cantarell,Noto Sans,sans-serif,BlinkMacSystemFont,Segoe UI,Helvetica,Arial,sans-serif,Apple Color Emoji,Segoe UI Emoji,Segoe UI Symbol; margin: 0; color: #1c1e21; } h1 { font-size: 2rem; line-height: normal; } a { color: #f38020; text-decoration: none; } #content { grid-area: content; margin-left: 2rem; margin-right: 3rem; line-height: 1.5rem; z-index: -5; max-width: 800px; } /style> body>article idcontent> h1>Cloudflare Research: TLS handshake size experiment/h1> p> On a small fraction of our challenge pages, weve been running an experiment to measure the performance impact of a larger TLS handshake. We were performing these measurements to understand the trade-offs involved when switching to post-quantum secure ciphers and signature schemes. /p> h2>What was the experiment?/h2> p> For challenge pages that are part of the experiment, we launched two background connections. On these background connections, we disabled certificate compression and added one or more dummy certificates to the server certificate chain to increase the size of the TLS handshake. These changes do not impact the security of the connection. /p> h2>Read about the results/h2> We a hrefhttps://blog.cloudflare.com/sizing-up-post-quantum-signatures/>published results on our blog/a>. h2>Contact/h2> p> You can reach us directly at a hrefmailto:ask-research@cloudflare.com>ask-research@cloudflare.com/a> with questions and fe
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]