When the government accuses a service member of misconduct tied to an anonymous handle, a throwaway email account, or a profile that never carries the member’s real name, the prosecution faces a threshold problem that has nothing to do with whether the words themselves are offensive. Before a panel can consider a single screenshot, the government must clear an evidentiary gate: it has to show that the accused is the person behind the pseudonym. That gate is authentication, and in a court-martial it is governed by Military Rule of Evidence 901.
The governing standard is low but not automatic
Military Rule of Evidence 901(a) states that the requirement of authentication is satisfied by evidence sufficient to support a finding that the item is what its proponent claims it to be. This is a deliberately modest bar. The military judge does not decide that the accused actually authored the posts; the judge decides only whether a reasonable panel could find that he did. If that threshold is met, the evidence comes in and the weight question goes to the members.
The Court of Appeals for the Armed Forces applied this framework to digital evidence in United States v. Lubich, 72 M.J. 170 (C.A.A.F. 2013), confirming that the same Rule 901(a) sufficiency standard governs electronically stored information. The Military Rules of Evidence track the Federal Rules of Evidence closely here, so federal authentication case law is persuasive in the military forum.
Why pseudonymous content raises the stakes
A signed letter or a recorded confession links itself to its author. A pseudonymous account does not. Anyone with the login credentials, or anyone who guessed a weak password, can post under the same name. For that reason, courts treat the question of authorship as a distinct authentication problem, separate from confirming that a screenshot accurately depicts what appeared on a screen. Establishing that a printout faithfully captures a web page does not establish who typed the words. The proponent must take the additional step of linking the account to a particular individual to establish authorship.
This distinction matters in identity-based misconduct charges, where the entire theory of guilt depends on the accused being the speaker or actor. If the defense can create genuine doubt that the accused controlled the account, the foundation collapses.
The methods the government actually uses
Authentication of pseudonymous conduct is almost always circumstantial, built from several of the methods listed in Rule 901(b):
Testimony of a witness with knowledge under Rule 901(b)(1). A witness who saw the accused logged into the account, who received messages from it and later confirmed the sender in person, or who watched the accused post can supply direct linkage.
Distinctive characteristics under Rule 901(b)(4). This is the workhorse provision for online content. The rule allows authentication from the appearance, contents, substance, internal patterns, or other distinctive characteristics of the item, taken together with all the circumstances. In practice the government points to details such as references to the accused’s family members, coworkers, or unit; private facts known only to the accused; a recurring writing style, slang, abbreviations, or emoji usage that matches the accused’s known communications; and identifying photographs.
Process or system evidence under Rule 901(b)(9). Where the evidence is the output of a system, testimony describing the system and showing it produces accurate results can authenticate the result. This supports forensic extractions from a seized device.
Self-authenticating certifications under Rule 902(13) and 902(14). A qualified custodian’s certification can establish that a record was generated by an electronic process or that copied data is identical to the original. Critically, that certification authenticates the record and the integrity of the copy; it does not by itself prove authorship. Where authorship is contested, the proponent still has to supply the additional linking evidence described above.
Tying the handle to the person
The strongest cases stack multiple threads. Subscriber and IP records obtained from a service provider may tie the account to the accused’s residence or government network credentials. Device forensics may show the account logged in from a phone seized from the accused. Content may reveal nonpublic biographical detail. Login activity may correlate with times the accused was demonstrably at a particular terminal. No single thread is required, and the absence of any one of them is not fatal, because the standard asks only whether the combined showing would let a reasonable factfinder conclude the accused was the author.
Where these cases break down
The recurring defense theme is the shared-or-stolen-account argument: that someone else had access, that the device was unsecured, or that the handle was spoofed. Because authentication is only a sufficiency screen, this argument usually does not keep the evidence out. Instead it becomes a weight argument the defense presses to the panel, and it can succeed there. The government’s foundation should therefore anticipate it, closing off alternative-user theories with metadata, exclusive-access proof, or content only the accused would know.
A second pressure point is the chain of custody and integrity of the digital item itself. Screenshots are easy to alter, and metadata can be lost when content is copied by hand rather than captured forensically. A defense challenge under Rule 901 to the accuracy of the capture, or a Rule 403 argument that an unreliable exhibit is more prejudicial than probative, can exclude sloppy collection even when authorship is otherwise provable.
The practical takeaway
In identity-based misconduct charges, the fight is rarely about what the words say. It is about proving, through layered circumstantial evidence, that the accused is the person behind the pseudonym. The government does not need certainty; it needs enough to support a reasonable finding of authorship under Military Rule of Evidence 901(a). The defense does not need to prove someone else did it; it needs to make the alternative plausible enough that the panel will not be persuaded beyond a reasonable doubt. Service members facing these allegations should expect the case to turn on forensic linkage, account access, and the distinctive fingerprints of their own communications, and they should retain counsel who understands how military judges screen digital evidence before it ever reaches the members.
Disclaimer
This article is provided strictly for general educational and informational purposes. It is intended to explain how the Uniform Code of Military Justice (UCMJ), the Rules for Courts-Martial, the Military Rules of Evidence, and related military administrative processes work as a matter of public legal education. It does not constitute legal advice, a legal opinion, or a recommendation about any particular case, and it is not a substitute for advice from a qualified military defense attorney who can evaluate the specific facts and command, service, and jurisdictional circumstances involved.
Reading this article, or contacting any website on which it appears, does not create an attorney-client relationship between the reader and any law firm, attorney, or author. Every court-martial, nonjudicial punishment action, administrative separation, and security-clearance matter turns on its own facts, the charged articles, the convening authority, the service branch, and the evidence, and outcomes vary widely from one case to another.
Military law also changes over time. The Military Justice Act of 2016 (effective January 1, 2019) and subsequent National Defense Authorization Acts renumbered and rewrote many punitive articles, revised the Article 32 preliminary hearing, and altered sentencing, clemency, and appellate procedures. Statutes, regulations, executive orders, the Manual for Courts-Martial, and decisions of the service Courts of Criminal Appeals and the Court of Appeals for the Armed Forces may have been amended, superseded, or reinterpreted after this article was written, and article numbers or procedures cited here may have changed.
For these reasons, no reader should act or decline to act based on this content without first consulting a licensed attorney experienced in military justice about their own situation. The author and publisher make no warranty, express or implied, as to the accuracy, completeness, timeliness, or current applicability of the information provided, and disclaim any liability for any action taken or not taken in reliance on it. If you are facing investigation, charges, or an adverse administrative action, time limits may apply, and you should seek qualified counsel promptly.