Paste a CSR first. It starts with -----BEGIN CERTIFICATE REQUEST-----.This is a private key, not a CSR. It wasn't decoded or sent anywhere, and it has been cleared from the box. Never share a private key: if this one was pasted into another website or sent to anyone, generate a new key and CSR, and replace any certificate that uses it.This is a PKCS #12 (.pfx or .p12) file. It holds a private key, so it wasn't decoded. Upload the .csr file instead.This is an issued certificate, not a CSR. To check a certificate on a live server, use the {link}.SSL Certificate CheckerThis is a public key on its own, not a CSR. A CSR starts with -----BEGIN CERTIFICATE REQUEST-----.This is a PKCS #7 certificate bundle, not a CSR.This is a certificate revocation list (CRL), not a CSR.This is an SSH key, not a CSR.This is a PGP block, not a CSR.This block is labeled {label}, not CERTIFICATE REQUEST.The END line is missing. Copy the whole CSR, from -----BEGIN CERTIFICATE REQUEST----- to -----END CERTIFICATE REQUEST-----.Line {line} has a character that can't be in a CSR ({ch}). Copy the CSR again, without other text inside the block.The CSR text is incomplete. Copy it again, including the BEGIN and END lines.This doesn't look like a CSR. Paste the text that starts with -----BEGIN CERTIFICATE REQUEST-----, or upload the .csr file.This CSR is damaged: its structure can't be read. Copy it again from the original file.This CSR is cut short. Copy it again, including the last lines before the END line.That's too large to be a CSR.That file couldn't be read. Try again, or paste the CSR text instead.The decoder couldn't be loaded. Check your connection and try again.Something went wrong while reading this CSR. Copy it again and retry.CSR forDecoded CSRPKCS #10 v{v}{n} bytesSSL/TLSS/MIMEClient certificateCode signingBIMI (VMC or CMC)Document signingCA certificateThis CSR looks goodNo problems found. It's ready to send to your certificate authority.This CSR works, with 1 warningThis CSR works, with {n} warningsReview the warnings below. Some CAs may reject the request, or issue a certificate that doesn't cover everything you need.1 problem to fix before you order{n} problems to fix before you orderA certificate authority is likely to reject this CSR. Fix the problems below and generate a new one.Public keySignatureSANsSignature checkValidInvalidNot checkedChecks{p} of {n} passedHow to fixSubjectPublic keySubject Alternative NamesExtensions and attributesKey fingerprints and DANEGenerate a new key and CSROpenSSL viewCheckResultStatusPassWarningFailInfoFix firstReview{n} moreSignatureSignature algorithmKey type and sizeKnown key weaknessesPublic exponentPublic key pointSubject Alternative NamesCommon Name in the SANsHostname formatPublic namesWildcardIP addressesRepeated namesNumber of namesCountry codeDefault valuesState or provinceField lengthCharactersRepeated fieldsCombined fieldsEmail address in the subjectOrganizational unit (OU)SubjectBasic constraintsKey usageOCSP Must-StapleCT poison extensionCritical extensionsRepeated extensionsUnreadable extensionExtended key usageChallenge passwordCSR versionAttributes fieldExtra dataEncodingRequests pastedValid: signed by the private key that matches this public keyInvalid: the signature doesn't match the public keyInvalid: a {alg} signature can't come from a {key} keyInvalid: the signature is encoded incorrectlyNot checked: this browser has no signature support on this pageNot checked: browsers can't verify {alg} signaturesNot checked: browsers can't verify RSA-PSS with these parametersNot checked: the public key can't be readNot checked: this browser can't verify {alg} signatures{alg}Unknown algorithm ({oid}){alg}: MD5 is broken, and CAs reject it{alg}: SHA-1 is no longer considered safe{alg}: weaker than the SHA-256 CAs expect{alg}: the RSA-PSS parameters can't be readRSA {bits}-bitRSA {bits}-bit: smaller than the 2048-bit minimumRSA {bits}-bit: the size must be a multiple of 8RSA {bits}-bit: an unusual sizeRSA-PSS {bits}-bit: a key limited to RSA-PSS, which public CAs don't acceptECDSA {curve}ECDSA P-521: allowed, but not every CA accepts itECDSA {curve} with a compressed public keyECDSA with explicit curve parameters ({curve})ECDSA {curve}: a curve public CAs don't accept{key}: public CAs don't issue SSL/TLS certificates for it yet{key}DSA {bits}-bit: no longer accepted{key}: this key type can't signUnsupported key type ({oid}){key}: the key data is malformedNone found (ROCA, close primes, small factors)Not checked in this browserThe ROCA weakness (CVE-2017-15361): the private key can be worked outThe two primes are too close together: the key can be factored in secondsThe modulus is even: not a valid RSA keyThe modulus has a small factor ({p}): the key is broken{e}: not a valid RSA exponent{e}: lower than the 65537 most CAs expect{e}: larger than the 65537 most CAs expectThe public key isn't a valid point on {curve}{n} names: {list}1 name: {list}None, only the Common Name {cn}No hostname: no Common Name and no SANsNo hostname. Fine for some certificate types, but an SSL/TLS certificate needs one{cn} isn't in the SAN list{list}{name} ({why})empty namea URL, not a hostnamenot in xn-- forminvalid characterstrailing dotover 253 charactersan IP address written as a DNS namethe wildcard must be the whole first labela wildcard over a whole top-level domainan empty labela label over 63 charactersunderscores aren't alloweda label starts or ends with a hyphena reserved "--" labelan invalid xn-- labelInternal or reserved: {list}{list}: covers one level of subdomains{list}: only some CAs issue certificates for IP addressesListed more than once: {list}{n} names: many CAs allow at most 100{c}UK isn't an ISO code: the United Kingdom is GB{c}: use the two-letter code {hint}{c}: must be a two-letter ISO 3166 codeXX: means no country code{c}: not an ISO 3166 country code{c}: write it in capitals ({up})Tool defaults left in: {list}{st}: an abbreviation{field} has {n} characters; the limit is {max}{field} isn't encoded correctly: OpenSSL can't read this CSR{field} has characters its string type can't hold{field} contains control characters{field} has extra spaces{field} appears {n} times{list} share one field{email}: CAs leave it out of SSL/TLS certificates{ou}: public CAs leave the OU out of SSL/TLS certificatesEmpty: the CA uses the SANs insteadAsks for a CA certificate (CA:TRUE)Asks for certificate or CRL signingKey encipherment can't be used with an ECDSA keyAsks for OCSP Must-StapleContains the Certificate Transparency poison extensionUnknown critical extension: {list}More than once: {list}{ext} can't be read, and OpenSSL and CAs reject a CSR like thisThe Subject Alternative Name extension can't be read, and OpenSSL and CAs reject a CSR like thisAsks for {list}Present, stored in plain text in the CSRVersion {v}: only version 1 existsMissing (the standard requires it, even when empty){n} bytes after the end of the request were ignoredNot strict DER, which some CAs rejectOnly the first of {n} requests was decodedThe CSR was changed or damaged after it was signed. Copy it again from the original file, or generate a new CSR.Generate the CSR again with SHA-256. Current OpenSSL uses it by default; on older versions add -sha256.Generate a new key of at least 2048 bits (RSA), or an ECDSA P-256 key, and a new CSR.Generate a new 2048, 3072 or 4096-bit RSA key and a new CSR.If your CA rejects it, generate a 2048, 3072 or 4096-bit RSA key. Some CAs accept only those sizes.Generate a standard RSA key (openssl req -newkey rsa:2048) and a new CSR.If your CA rejects P-521, generate the key on P-256 or P-384.Generate the CSR from a key saved in the standard uncompressed form.Generate the key with a named curve (openssl ecparam -name prime256v1) and a new CSR.Generate a new key on P-256 or P-384, or an RSA 2048-bit key, and a new CSR.For a public SSL/TLS certificate, use an RSA 2048-bit or ECDSA P-256 key.Generate an RSA 2048-bit or ECDSA P-256 key and a new CSR.Don't use this key anywhere. Generate a new key with current software, or on a device with patched firmware, then a new CSR, and replace any certificate that uses the old key.Most CAs expect the exponent 65537, OpenSSL's default. Generate a new key if your CA rejects this one.Generate a new RSA key with the standard exponent 65537.Add every hostname as a Subject Alternative Name. Browsers only check SANs. Most CAs add the Common Name for you, but not other names such as www.Add the hostname as the Common Name and as a Subject Alternative Name.Add {cn} to the Subject Alternative Names so the certificate covers it.Fix or remove these names: {list}. A public certificate can only cover valid hostnames.Public CAs can't issue for internal names or private IP addresses. Use a public domain name, or an internal CA for internal-only services.Remove the repeated names.If your CA limits the number of names, split them across several certificates.Use GB, the ISO 3166 code for the United Kingdom.Use the two-letter ISO 3166 country code in capitals, such as US, GB or DE.Replace the default values with your real details, or leave those fields out: domain-validated certificates don't need them.Write the state or province out in full, for example California, not CA.Shorten {field} to {max} characters. A long hostname belongs in the SANs, and the Common Name can be left out.Generate the CSR again: {field} holds broken text that OpenSSL and most CAs refuse.Remove the extra spaces and special characters from {field}.Keep one value for {field}.Remove basicConstraints=CA:TRUE. Public CAs issue CA certificates only under a separate agreement.Remove keyCertSign and cRLSign from the key usage. Only CA certificates can use them.Remove keyEncipherment from the key usage, or leave key usage to your CA.Leave Must-Staple out unless your CA asks for it. It depends on OCSP, which Let's Encrypt has shut down and other CAs are retiring.Generate the CSR again without the poison extension. It belongs only in precertificates.Remove the unknown critical extension, or mark it non-critical.Generate the CSR again with a standard tool, with each extension once.Generate the CSR again and leave the challenge password empty.Generate the CSR again with a standard tool such as OpenSSL.Generate the CSR again with a standard tool such as OpenSSL.Copy only the request, from the BEGIN line to the END line.EmptyNone in this CSR{n} more names are checked but not listed here.Common nameSurnameSerial numberCountryLocalityState or provinceStreetOrganizationOrganizational unitTitleDescriptionBusiness categoryPostal codeNameGiven nameInitialsGeneration qualifierDN qualifierPseudonymOrganization identifierEmail addressUnstructured nameDomain componentUser IDJurisdiction localityJurisdiction stateJurisdiction countryAttribute {oid}AlgorithmRSARSA-PSSECDSA (elliptic curve)DSAKey size{n} bitsExponentCurveExplicit parameters ({curve})Point formatCompressedUncompressedSignature algorithmShow the modulusShow the public keyEmailRegistered IDDirectory nameOther nameSubject Alternative NameKey usageExtended key usageBasic constraintsSubject key identifierTLS featureCertificate policiesMicrosoft certificate templateS/MIME capabilitiesNetscape certificate typeNetscape commentLogotype (BIMI)Authority key identifierCRL distribution pointsAuthority information accessCT poisonCT timestampsName constraintsQualified certificate statementsExtension {oid}criticalCan't be readDigital signatureNon-repudiationKey enciphermentData enciphermentKey agreementCertificate signingCRL signingEncipher onlyDecipher onlyTLS server authenticationTLS client authenticationCode signingEmail protection (S/MIME)Time stampingOCSP signingBrand indicator (BIMI)IPsecSmart card logonDocument signingEncrypting file systemAny purposePDF signingCA: yesCA: nopath length {n}status_request (Must-Staple)status_request_v2Challenge passwordPresent (not shown)Unstructured nameWindows versionWindows request clientWindows key providerWindows enrollment valuesAttribute {oid}SHA-256 (hex)SHA-256 (Base64)TLSA record (DANE-EE)A DANE TLSA record pins this key, so you can publish it before the certificate is issued. For a mail server, add it at _25._tcp.<your MX host> next to the current record, switch certificates, then remove the old record.Check DANE recordsThe same SHA-256 from your private key and from the issued certificate:Not available in this browser.Same details, with the fixes applied. The new private key is saved to {key}: keep it on your server and send only {csr} to your CA.Same details with a new key. The private key is saved to {key}: keep it on your server and send only {csr} to your CA.Left out: {list}.{cn} added to the SANs.CopyCopiedCopy this with Ctrl+C (Cmd+C on a Mac), then press Enter.Copy all namesCopy the SHA-256 in hexCopy the SHA-256 in Base64Copy the TLSA recordCopy the OpenSSL commandCopy the OpenSSL viewCertificate issued? Check it's installed right.Once your CA issues the certificate, check its expiry, chain and hostname on your live server.Check SSL certificate