Can an Electronic Signature Be Forged or Disputed in Court?

Yes, an electronic signature can be forged, and it can be disputed in court, just like a handwritten one. That doesn't make it weak. US law gives electronic signatures the same legal effect as ink, and courts accept them every day. What decides a dispute is evidence: if someone says "that wasn't me," the party relying on the signature has to show who actually signed.

This guide covers how e-signature forgery really happens, how disputes play out, what courts have accepted and rejected, and what to do if you think your signature was faked.

Does an electronic signature hold up in court?

Yes, as a rule. The federal ESIGN Act says a signature or contract can't be denied legal effect just because it's electronic. The Uniform Electronic Transactions Act (UETA), adopted by 49 states and Washington, D.C., says the same, and adds that evidence of an electronic record or signature can't be excluded from a proceeding just because it's in electronic form. New York, the one holdout, has its own law that gives e-signatures the same validity as handwritten ones.

The European Union works the same way. Under the eIDAS Regulation, an electronic signature can't be refused legal effect or rejected as evidence just because it's electronic, and a qualified electronic signature (QES) has the same legal effect as a handwritten one. In Switzerland, a QES with a qualified time stamp is treated like a handwritten signature where the law requires written form.

There are exceptions. ESIGN doesn't cover wills, certain family law documents, or court filings, and courts set their own rules for what you file with them. For the full picture by country, see our e-signature legality hub and the United States page.

Valid, admitted, believed: what a court actually decides

Most articles blur three different questions. Keeping them apart makes disputes much easier to understand:

• Is it valid? Can this kind of signature legally sign this kind of document? For most business documents in the US, the EU, and Switzerland, an electronic signature can.
• Will the court admit it? Can it be used as evidence? Under ESIGN, UETA, and eIDAS, it can't be rejected just for being electronic.
• Will the court believe it? Did this particular person actually sign this particular document? This is where disputes are won or lost, and it comes down to evidence.

Almost every reported e-signature dispute is about the third question. Nobody argues that e-signatures are illegal. They argue "that wasn't me" or "I never meant to sign."

How do electronic signatures get forged?

Forging an electronic signature rarely means faking the look of a signature. It usually means getting into the process that's supposed to prove who signed. The common routes:

• Email account takeover. Most signing links go to an email address. Whoever controls that inbox can open the link, so a hacked or shared mailbox is the most common weak point.
• Someone signs on another person's behalf. An office manager, an assistant, or a family member clicks "Sign" for someone else, sometimes with permission, often without it.
• A pasted signature image. Someone copies a picture of your signature from an old document and drops it onto a PDF. That's not a signing process at all, just an image.
• Editing after signing. The signature is real, but the document was changed afterward, for example a different price or date.
• Phishing that imitates a signing request. A fake "please sign" email leads to a page that steals your login. This attacks your account rather than a specific document.

Is an electronic signature easier to forge than a wet signature?

It depends on how it was collected. A pasted image or a typed name in an email is easy to fake and hard to prove. A signature collected through a signing platform is a different story, because the platform records far more than the mark itself.

Compare what each leaves behind. A forged ink signature gives you one piece of paper and, if it goes to court, a handwriting expert's opinion. A platform signature comes with an audit trail: the email address the request went to, any extra verification the signer passed, timestamps for when the document was sent, viewed, and signed, and the IP address and device used. A forger has to beat all of that, not just copy a squiggle.

Certificate-based signatures add another layer. Advanced and qualified signatures seal the document with a cryptographic fingerprint, so any edit after signing shows up as a broken signature in a PDF reader. That closes the "edit after signing" route almost completely.

How are electronic signatures disputed?

Challenges usually take one of five forms:

• Identity: "I didn't sign that." The most common challenge, and the one courts spend the most time on.
• Intent: "I didn't mean to sign." For example, a typed name at the bottom of an email that the sender says was just a sign-off. See whether a typed signature is legally binding.
• Consent: in consumer deals, ESIGN requires the consumer to agree to doing business electronically, with certain disclosures, before electronic records can replace paper ones.
• Integrity: "The document I signed said something else." This is where tamper evidence matters.
• Wrong document type or forum: the document falls under an exception, or a court's own rules demand an original ink signature.

Who has to prove an electronic signature is real?

The party relying on the signature. Under UETA, an electronic signature belongs to a person if it was "the act of the person," and that act can be shown in any manner, including how well a security procedure worked. The official comment to UETA adds that, just like with paper, the other side can bring evidence of forgery to rebut it.

In court, evidence has to be authenticated, meaning there has to be enough proof that it is what it claims to be. The Federal Rules of Evidence specifically allow this through evidence describing a process or system and showing it produces an accurate result. That's exactly what an e-signature audit trail is.

California courts have spelled out how this works in practice. Attaching the signed document is enough to start. But once the other side says under oath that they didn't sign, the party relying on the signature has to prove it's authentic, more likely than not.

What have courts said about disputed e-signatures?

The published cases tell a consistent story: courts don't reject e-signatures for being electronic. They reject weak explanations of how the signature got there.

• Not enough explanation (rejected). In a 2014 California appeals decision, an employer couldn't enforce an arbitration agreement because its manager only stated that the employee had signed electronically, without explaining how the signature and date got there or why only he could have placed them. The court said the burden wasn't hard to meet, but it wasn't met.
• Process explained (accepted). In a 2016 California appeals decision, the employer filed a declaration describing the unique username and password, the steps needed to sign, and the date, time, and IP address recorded on the document. That was enough, and the signature was attributed to the employee.
• A "signed by" stamp alone (rejected). In a 2019 California appeals decision, a contract showed a well-known platform's "signed by" label, an ID code, and an "ID verification complete" note. The company offered no evidence of how the signing process worked, so the label on its own didn't prove who signed.
• Shared access (rejected). In a 2021 California appeals decision, the login an employee supposedly used relied on details an HR manager also had, and there was evidence she had completed onboarding for other employees. The evidence was at best evenly split, so the employer lost.

One more case gets misquoted a lot. A 2016 federal bankruptcy court decision refused e-signatures on bankruptcy filings. It's often cited as "a US court rejected e-signatures," but it was about that court's own rule for filings, which ESIGN doesn't cover. It says nothing about whether e-signed contracts are valid.

The lesson for anyone sending documents: keep evidence that explains who signed and how, not just a signature on a page.

What makes a digital signature invalid?

A digital signature is the certificate-based technology behind advanced and qualified signatures (see electronic vs. digital signatures). A PDF reader will flag it as invalid or untrusted when:

• The document changed after signing. eIDAS requires an advanced signature to be linked to the signed data so that any later change is detectable, and that's exactly what the check catches.
• The certificate was revoked or had expired at signing time.
• The certificate doesn't chain back to a trusted provider, so the reader can't confirm who issued it.
• The file was re-saved or re-exported in another editor, which can break the seal even when nobody meant to tamper with it.

Our guide on how to verify an electronic signature walks through each check step by step.

Can you sign someone else's name with their permission?

Sometimes, but it's risky and often avoidable. In many situations a person can authorize someone else, an agent, to sign for them, and the rules depend on the document and the jurisdiction. Some documents must be signed by the person themselves, and some require written authority, such as a power of attorney.

With e-signatures, the cleaner route is to not sign as someone else at all. Ask the sender to address the request to the person who actually has to sign, or have the authorized person sign under their own name and title. That way the audit trail matches reality. A signature placed by someone else under your name is exactly the pattern courts have rejected. If you're unsure, ask a lawyer before signing.

What should you do if you think your electronic signature was forged?

1. Don't ignore it. If you rely on or act under the document, you can make the problem harder to undo.
2. Ask for the evidence. Request the audit trail or certificate of completion from whoever sent the document. Signing platforms record when it was sent, opened, and signed, and from which IP address and device.
3. Compare it with your own records. Was that your email address? Were you somewhere else at that time? Do you recognize the device or location?
4. Secure your email. Change your password, turn on two-factor authentication, and check for forwarding rules or logins you don't recognize, since the inbox is the usual way in.
5. Tell the sender and the platform in writing that you dispute the signature, and keep copies.
6. Talk to a lawyer, and to the police if money or property is involved. Forging an electronic signature can be a crime: New York's forgery law, for example, expressly covers computer data, and schemes carried out over email can fall under federal wire fraud.

How to make your e-signatures hard to dispute

If you send documents for signature, a few habits make a later challenge much easier to answer:

• Match verification to the risk. An email link is fine for routine documents. Add a passcode, an SMS code, or an ID check for contracts where identity really matters. Our guide to electronic signature authentication explains each method.
• Never use shared logins or sign on behalf of the people who are supposed to sign.
• Use a higher signature level when the document calls for it. Advanced and qualified signatures add certificate-based protection. See the types of electronic signatures.
• Keep the evidence with the contract. Download the audit trail or certificate of completion and file it with the signed document.
• Know how your platform works. If you ever have to explain the signing process to a court, you'll want to describe it, not just point at a logo.

For the wider picture, see our electronic signature security best practices.

How Sign.Plus helps you prove who signed

Sign.Plus is built to answer the question courts actually ask: who signed, and how do you know?

• Verification chosen per signer. With recipient verification, you can require a passcode, an SMS code, or an ID check with a government ID and a liveness check, and mix them within a single request. With verification on, recipients can't even preview the document until they pass the check. With ID Check, the request can't be reassigned to someone else.
• A tamper-proof audit trail. Every document logs each action, such as viewed, signed, or declined, with the person's name, email address, timestamp, IP address, and device, plus which verification step they completed, for example "Verified by ID Check."
• A Certificate of Completion. The Certificate of Completion collects that evidence in one downloadable file. It's kept separate from the signed document by default to protect signers' personal data. Sign.Plus doesn't put a clock on that evidence: completed documents stay available while you use them, and the audit trail and Certificate of Completion are kept indefinitely.
• All three signature levels. Simple Electronic Signatures are the default, and Advanced and Qualified signatures are available on paid plans. Qualified signatures run through Swisscom Trust Services, a qualified trust service provider that verifies the signer's identity and issues the qualified certificate.

All of this runs on a platform certified to ISO/IEC 27001:2022 by EY CertifyPoint, with a SOC 2 Type 2 report from EY.

Want signatures that come with their own proof? Start signing with Sign.Plus.