Every certificate has a Subject field (who or what the certificate identifies — typically your domain, and for OV/EV certificates, your organization) and an Issuer field (which CA signed and issued it). Reading these two fields together answers the two most basic questions about any certificate: who is this for, and who vouches for it?
What's actually in the Subject field
For a modern domain-validated certificate, the Subject is often minimal — sometimes just the Common Name, with the real hostname coverage living in the SAN field instead. For OV and EV certificates, the Subject additionally includes verified organization name, location, and sometimes registration details.
Checking it yourself
In any browser, click the padlock, then view certificate details — Subject and Issuer are shown near the top. This is the fastest way to confirm you're not looking at an unexpected or fraudulent certificate: the Issuer should be a CA you recognize, and the Subject should clearly match the domain you intended to visit.
What these two fields together actually let you verify
Reading Subject and Issuer side by side answers the two most basic trust questions about any certificate at a glance: who is this certificate for, and who is vouching for that claim — a quick, practical check worth doing any time a certificate warning or unexpected detail prompts closer inspection.
Why OV and EV certificates carry meaningfully more in the Subject field
A DV certificate's Subject is often minimal, sometimes just the Common Name, with actual hostname coverage living in the SAN field instead. OV and EV certificates additionally embed verified organization name, location, and sometimes registration details directly in the Subject, reflecting the more rigorous validation those tiers underwent.
A quick way to spot a fraudulent certificate using just these two fields
If the Issuer field shows a CA you don't recognize, or the Subject doesn't clearly and exactly match the domain you intended to visit, that's a concrete, actionable signal worth investigating immediately, rather than clicking past a warning based on the assumption it's probably just a routine misconfiguration.
Why self-signed certificates have identical Subject and Issuer fields
Because a self-signed certificate is signed by its own private key rather than a separate CA's, the entity vouching for it and the entity being vouched for are the same — resulting in identical Subject and Issuer fields, a quick, reliable way to visually identify a self-signed certificate at a glance.
How to use these two fields to detect a suspicious certificate quickly
If the Issuer field shows an unfamiliar CA name for a domain you regularly trust, or the Subject doesn't precisely match the domain you intended to visit, that's a concrete, specific signal worth investigating immediately rather than assuming it's a routine, harmless misconfiguration.
Why these two fields are worth checking more often than most people do
Given how quickly and easily Subject and Issuer can be checked, via a couple of clicks on any certificate, making it a habit whenever something about a connection feels unexpected costs almost nothing and can catch a genuine problem early.
What additional fields commonly appear alongside Subject and Issuer worth knowing
Beyond Subject and Issuer, the Validity period, Serial Number, and Subject Alternative Name fields round out the handful of fields most worth understanding for practical, everyday certificate troubleshooting — together these five cover the large majority of what you'd ever need to check manually.
A closing thought
A quick closing thought: these two fields, checkable in seconds on any certificate, are worth making a habit of glancing at whenever something about a connection feels even slightly unexpected.