SSL Certificate - Organization Validation (OV) Step 2 - Locality Presence

Locality Presence is Step 2 of the Organization Validation (OV) process you complete when ordering an OV SSL certificate. In this step the Certificate Authority (CA) confirms that your organisation genuinely exists at the physical address you listed, in the city, state or region, and country you claim to operate from. It is a verification of place, sitting between Step 1 (Organization Authentication) and Step 3 (Telephone Verification).

What Locality Presence actually checks

An OV certificate embeds your legal organisation name and location details directly into the issued certificate, so the CA has to be satisfied those details are real before it signs anything. Locality Presence is the part of that vetting that ties your business to a verifiable address. Rather than take the address on trust, the CA cross-references it against independent, authoritative records.

Acceptable evidence of locality usually falls into one of these groups:

• A listing in an official government or business registry that shows your organisation at the stated address.
• A recognised third-party business directory (for example, a national telephone directory or an established commercial database).
• A current utility bill, bank statement, lease agreement, or similar document issued to the organisation at that address.

The exact documents the CA will accept depend on your country and how your business is registered, so it is worth having more than one form of proof ready. If the details on your order do not match the source the CA checks, the request stalls until the mismatch is resolved, which is the single most common cause of OV delays.

Where this step sits in the full OV sequence

Organization Validation is a staged process. Passing Locality Presence alone does not issue the certificate; each step has to clear in turn:

1. Step 1 - Organization Authentication: confirming the organisation is a real, registered legal entity.
2. Step 2 - Locality Presence: confirming the organisation is present at the claimed address (this article).
3. Step 3 - Telephone Verification: confirming a verifiable phone number tied to the organisation.
4. Step 4 - Domain Authentication: confirming you control the domain the certificate will secure.
5. Step 5 - Final Verification Call: a closing call to a verified number to authorise issuance.

We provide a downloadable Locality Presence (OV) guide as part of the ordering flow that walks through the documents you can submit and how the check is carried out. Having your paperwork lined up before you start keeps the whole sequence moving.

How to clear Locality Presence quickly

• Use your exact legal organisation name and registered address, matching them character for character to your official records.
• Make sure your business is discoverable in at least one authoritative source (a government registry or a well-known directory) at that address.
• Keep a dated utility bill, lease, or bank statement to hand in case the CA asks for supporting proof.
• If you have recently moved or re-registered, update the public record first, since the CA checks live sources.

OV, DV, and choosing the right certificate

Not every certificate involves these checks. Domain Validated (DV) certificates, such as the free ones issued by Let's Encrypt, confirm only that you control the domain and skip the organisation and locality vetting entirely. OV certificates add the identity layer described here, which is why they take longer to issue but display your verified organisation details in the certificate itself. If you run client-facing sites or want that verified identity on record, OV is the appropriate tier; if you simply need traffic encrypted, DV is enough.

You can review the full range and start an order on our SSL certificates page, and the rest of the OV steps are covered in the SSL certificates FAQ. If a locality check stalls and you are not sure why, our support team can tell you which source the CA is querying and what proof will clear it.