Endpoint
A public website or service that NodeVane can connect to and inspect, such as www.example.com or api.example.com.
Glossary
You do not need to be a TLS or PKI expert to use NodeVane. Here are the terms you may see in the app and what they actually mean.
A public website or service that NodeVane can connect to and inspect, such as www.example.com or api.example.com.
The digital certificate a website or service presents when a secure HTTPS/TLS connection is made. NodeVane records the certificate it actually observes on an endpoint.
A way to start with one domain and look for related public hostnames. NodeVane then checks which candidates are actually serving TLS.
A hostname found during Discovery that might be publicly used. It is only a candidate until NodeVane actively checks it.
NodeVane successfully connected to the endpoint over TLS and observed the certificate it is currently presenting.
An endpoint that is already part of your NodeVane inventory.
NodeVane found the hostname but could not successfully verify a TLS service on it during that Discovery run.
A Discovery candidate that NodeVane found but did not actively check during that run, usually because the per-run verification limit was reached.
The issuer identity recorded in the leaf certificate, usually a certificate authority such as Let's Encrypt or DigiCert. This does not mean NodeVane observed the full certificate chain.
Short for Subject Alternative Name. These are domain names listed inside a certificate as names it can be valid for. A SAN does not prove that the certificate is actually deployed on every listed name.
A SHA-256 identifier calculated from the exact certificate NodeVane observed. It lets NodeVane distinguish one certificate from another.
The period during which a certificate is valid, including when it becomes valid and when it expires.
The collection of public endpoints and certificates you have chosen to keep track of in NodeVane.
Public logs of issued TLS certificates. NodeVane can use CT data to find possible hostnames during Discovery, but CT data alone does not prove that a hostname is currently live.
Previous observations kept by NodeVane so you can see when a certificate or its deployment changed over time.