Will Quantum Computing Make HTTPS Obsolete?
No: quantum computing is not expected to make HTTPS obsolete, but a sufficiently powerful, fault-tolerant quantum computer could weaken some cryptographic methods HTTPS relies on. The likely response is to update those methods—especially public-key key exchange and signatures—while keeping HTTPS as the protocol for protecting web connections.
What HTTPS Does
HTTPS is HTTP carried over Transport Layer Security (TLS). It protects the connection between a browser and a website by helping authenticate the server, negotiate encryption keys, and encrypt and check the integrity of data sent over the connection. It does not make a website trustworthy, prevent every kind of fraud, or conceal all metadata, such as the fact that a connection was made to a particular service.
Several cryptographic jobs are involved, and they do not all face the same quantum risk. In a typical TLS connection, public-key cryptography helps establish shared secret keys and authenticate the server. Symmetric encryption then protects the traffic, while hash functions support integrity checks and other protocol operations. HTTPS is a framework that can use different algorithms; it is not one fixed cipher that must be discarded wholesale.
Why Quantum Computers Matter
Quantum computers use quantum states to perform certain calculations differently from classical computers. The best-known concern for internet cryptography is Shor’s algorithm: on a large, reliable, fault-tolerant quantum computer, it could solve the mathematical problems underlying widely used public-key systems such as RSA and elliptic-curve cryptography far more efficiently than known classical methods.
That does not mean today’s quantum machines can decrypt ordinary HTTPS traffic at will. The machines needed to run those attacks at useful scale do not currently exist. Building one would require substantial advances in error correction, hardware scale, and reliability. Researchers cannot give a dependable date for when such a machine might be available.
Grover’s algorithm is another often-mentioned quantum algorithm. It can speed up brute-force search in principle, but its effect on symmetric encryption is different: it offers a quadratic, not an exponential, speedup. Using appropriately sized symmetric keys can provide a substantial margin against this risk. This is one reason the quantum threat is not a single, uniform break of all cryptography.
Which Parts of HTTPS Need to Change?
The most urgent concern is public-key cryptography used in key establishment and digital signatures. If a future attacker could break the public-key method protecting a recorded TLS handshake, they might be able to recover the session key and read the captured traffic, depending on the handshake design and what information was recorded. A server’s signature scheme also matters for proving that the connection is genuinely associated with its certificate.
Forward secrecy can limit the consequences of a later theft of a server’s long-term private key: past session keys are not simply derived from that key. But it does not by itself protect recorded handshakes from a future quantum attack on the key-exchange mathematics. The precise exposure depends on the algorithms and protocol configuration used.
Post-quantum cryptography (PQC) refers to cryptographic algorithms designed to resist attacks by both classical and quantum computers. These algorithms run on conventional computers; adopting them does not require a quantum computer in a browser or server. Standards bodies have published initial post-quantum cryptography standards, including algorithms for key establishment and digital signatures. Protocol designers and software providers are working to incorporate suitable algorithms into real systems.
What “Harvest Now, Decrypt Later” Means
Some adversaries may collect encrypted information today in hopes of decrypting it if they gain access to a capable quantum computer later. This is called a “harvest now, decrypt later” risk. It matters most for information that must remain confidential for many years, such as sensitive records or long-lived industrial secrets—not because current HTTPS is already easily broken, but because stored ciphertext may outlast the cryptographic protection used to create it.
Organizations with long confidentiality requirements should assess how long data needs protection, which systems use vulnerable public-key algorithms, and how difficult those systems will be to update. Individuals generally cannot change a website’s TLS configuration themselves; their practical protection depends on browsers, operating systems, websites, and network services adopting secure updates.
How the Transition Can Happen
Replacing cryptography across the web is a coordinated engineering task. Browsers, web servers, certificate systems, network equipment, and software libraries must support compatible choices. New algorithms can have different key sizes, signature sizes, performance costs, and implementation requirements, so they need careful testing at internet scale.
A transition may use hybrid key establishment: a connection combines a conventional method with a post-quantum method, so the shared secret remains protected if at least one component resists the relevant attacks and the combination is designed correctly. This is a migration technique, not a guarantee against every implementation flaw. Systems also need ways to issue, validate, and rotate credentials using updated signature algorithms.
For website operators, sensible preparation includes:
- Inventory TLS libraries, servers, certificates, and devices that terminate or inspect encrypted traffic.
- Keep software and cryptographic libraries current, and follow the supported migration guidance from their maintainers.
- Identify data whose confidentiality must last for years, then prioritize systems handling it.
- Test post-quantum or hybrid options in supported environments before broad deployment, including compatibility and performance.
Users should install browser and operating-system security updates and avoid treating a padlock icon as proof that a site’s content is honest or safe. The icon indicates aspects of the encrypted connection, not the site’s motives or the accuracy of its claims.
Will HTTPS Still Be Used?
Yes. HTTPS solves a continuing problem: protecting web communication against eavesdropping and tampering while authenticating the server. Quantum computing challenges particular cryptographic tools, not the need for secure web transport. TLS can evolve to use new key-establishment and signature algorithms while preserving the familiar HTTPS experience.
It is also misleading to say that quantum computers will “break the internet” all at once. Risk depends on machine capability, algorithm choice, how long information must remain secret, and how quickly systems migrate. The transition is important precisely because cryptographic changes take time—not because HTTPS has already become useless.
Frequently Asked Questions
Can a quantum computer decrypt my HTTPS traffic today?
No publicly known quantum computer can break the public-key cryptography used in ordinary HTTPS at practical scale. Current connections still benefit from modern TLS implementations and software updates.
Will HTTPS need to be replaced by a new protocol?
Not necessarily. HTTPS can continue using TLS while TLS adopts quantum-resistant algorithms. The visible web address and basic purpose of HTTPS can remain the same even as cryptographic components change.
Does post-quantum mean encryption performed by a quantum computer?
No. Post-quantum cryptography is designed to resist quantum attacks but generally runs on ordinary computers. “Quantum” describes the threat model, not the equipment required to use it.
Should I stop using websites that have HTTPS?
No. HTTPS remains important protection. Use current browser and device updates, and remember that encryption cannot guarantee that a site is legitimate, accurate, or free of harmful content.
What is the biggest near-term concern?
For data that must remain secret for a long time, the main concern is adversaries storing encrypted traffic now and attempting decryption later. Organizations should plan migration based on their data’s confidentiality lifetime and system dependencies.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.