REGEXVAULTv2.0
Security/Certificates & PKI
Verified Safe

Certificate Fingerprint (SHA-256) Regex for Java

/^[0-9A-F]{2}(?::[0-9A-F]{2}){31}$/i

What this pattern does

This page provides a well-structured, multi-part regular expression for matching certificate fingerprint (sha-256), ported and verified for Java. In security-sensitive code, using an unverified regex can open the door to both false positives and denial-of-service attacks. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

Java
// Certificate Fingerprint (SHA-256)
// ReDoS-safe | RegexVault — Security > Certificates & PKI

import java.util.regex.Pattern;

public class CertificateFingerprintSha256Validator {
    private static final Pattern PATTERN =
        Pattern.compile("^[0-9A-F]{2}(?::[0-9A-F]{2}){31}$");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("2B:8F:1B:57:33:0D:BB:A2:D0:7A:6C:DD:EC:1A:57:D0:5D:FB:F9:29:35:46:8E:11:33:46:93:D0:F2:CC:54:CA")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
2B:8F:1B:57:33:0D:BB:A2:D0:7A:6C:DD:EC:1A:57:D0:5D:FB:F9:29:35:46:8E:11:33:46:93:D0:F2:CC:54:CA2B:8F:1B:57:33:0D:BB:A2:D0:7A:6C:DD:EC:1A:57:D0:5D:FB:F9:29:35:46:8E:11:33:46:93:D0:F2:CC:54
2B8F1B5733D0BBA2D07A6CDDEC1A57D05DFBF929354682E11334693D0F2CC54CA

When to use this pattern

This pattern is drawn from the Security > Certificates & PKI category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Certificate pinning (HPKP) has largely been deprecated for public web because a misconfigured pin can take down a site. Use Certificate Transparency (CT) logs and CAA DNS records instead for web PKI.

Technical Notes

SHA-256 fingerprint = 256 bits = 32 bytes = 64 hex chars = 32 colon-separated pairs. Used to verify a certificate's identity (pin it) in TLS certificate pinning, SSH known_hosts, and manual certificate verification.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern