Are 1024-Bit DKIM Keys Still Secure?
DKIM uses digital signatures to verify that an email was signed by a particular domain and hasn’t been modified in transit. These signatures are typically based on RSA: The sender signs the message using a private key and the receiver verifies the signature using the corresponding public key published in the domain’s DNS records.
RSA security relies on the difficulty of factoring large numbers into their prime factors. For example, 77 can be factored into 7 × 11. That’s trivial for small numbers, but becomes computationally expensive for the large numbers used in RSA public keys. If an attacker can factor the modulus of an RSA public key, they can derive the corresponding private key.
To help answer the question of how difficult it is to factor the large numbers used in RSA, RSA Laboratories launched the RSA Factoring Challenge in 1991. It published a series of increasingly large numbers, each the product of two secret primes, and challenged researchers to factor them. Before September 2026, the largest successfully factored challenge number was RSA-250, a 250-digit (829-bit) number factored in February 2020.
In September 2026, that six-year-old record was broken twice. On September 9, Eric Lu at Cognition announced the factorization of RSA-260, a 260-digit (862-bit) number. Just ten days later, on September 19, Stephen Weis factored RSA-896, an 896-bit number. Both used GPU-optimized implementations of the general number field sieve (GNFS), demonstrating how advances in software and hardware can make factoring increasingly large RSA numbers more practical.
For RSA-260, Lu used an AI agent to optimize CADO-NFS, an open-source implementation of GNFS. This included developing a GPU-optimized lattice siever and improving several other parts of the software. The factorization required approximately 13.5 GPU-years of computation, corresponding to an estimated cost of around $414,000.
But what about RSA-1024, a key size that’s still used for DKIM signatures? Lu estimates in his article that factoring a 1024-bit RSA modulus would require approximately 1,050 GPU-years. At an assumed GPU rental price of $3.50 per hour, that works out to $32.3 million.
This is an estimate, not the cost of an actual RSA-1024 factorization. It’s based on extrapolating the RSA-260 results using the expected scaling of GNFS. Further optimizations could reduce the cost, and hardware prices will likely change over time.
Still, $32.3 million is a substantial investment. It’s far beyond the budget of an ordinary attacker, but potentially within reach of well-funded organizations with access to large GPU clusters. That makes the recent factoring records particularly relevant for anyone still relying on 1024-bit RSA keys for DKIM.
What Does This Mean for DKIM Security?
DKIM public keys are published in DNS, where anyone can retrieve them. An attacker could take a domain’s public DKIM key and attempt to factor its RSA modulus to recover the corresponding private key.
If successful, the attacker could use that private key to sign forged emails that pass DKIM verification, without needing access to the legitimate sender’s infrastructure. If the DKIM signing domain aligns with the domain in the From: header, those emails could also pass DMARC, even if SPF fails. Even a DMARC policy of p=reject wouldn’t protect against this attack.
The current DKIM standards already recommend using longer keys. RFC 8301 requires RSA keys to be at least 1024 bits long, but recommends 2048 bits or more. Google’s email sender guidelines also accept 1024-bit DKIM keys while recommending 2048 bits.
So, are 1024-bit DKIM keys still secure? For most attackers, factoring them remains impractical as of November 2026. But given the recent progress in RSA factorization, there’s little reason to continue relying on 1024-bit keys. Using 2048-bit RSA keys provides a substantially larger security margin and is the recommended choice for DKIM.
Check Your DKIM Key Length with DMARC Checker
To check your DKIM key length, visit DMARC Checker and send a test email to the address generated for you on the page. Once your email arrives, you’ll automatically be redirected to a report showing your email authentication results. You’ll also receive a link to the report via email.
The report verifies your DKIM signature and checks the length of the public RSA key published in DNS. If a 1024-bit key is detected, you’ll see the following warning:
Warning: The public RSA key in the p tag is 1024 bits. While still considered secure, it’s advised to use keys of 2048 bits.If you’re still using a 1024-bit key, consider upgrading to 2048 bits. Make sure your emails are successfully signed with the new key before removing the old one.
If you send emails through multiple providers, test each one separately. Different providers may use different DKIM keys.