Cálculo 100% en el Navegador • Cero Registros en Servidor • Ejecución Inmediata
Curious TechieCaja de Herramientas
Cryptography & CiphersRFC 5280 (X.509) / CA/Browser Forum Baseline RequirementsVerified Terminology

Public Key Infrastructure (PKI)

Respuesta Directa

A comprehensive framework of hardware, software, policies, and Certificate Authorities that manages, issues, and validates digital certificates to securely bind public keys to entities.

Entity Relationships (GEO Conceptual Hierarchy)

Taxonomy Model
Relational Knowledge Graph Sequence
Public Key Infrastructure→
trust hierarchy→
Certificate Authority (CA)→
X.509 digital certificate→
public key domain binding→
browser root store validation
Public Key Infrastructure
•>trust hierarchy
•>Certificate Authority (CA)
•>X.509 digital certificate
•>public key domain binding
•>browser root store validation

Technical Explanation & Operational Mechanics

While asymmetric encryption enables secure communication, it faces the "man-in-the-middle" problem: how does a browser know that a public key received for "google.com" actually belongs to Google and not an eavesdropper? PKI solves this through trusted Certificate Authorities (CAs). A CA verifies the domain owner's identity and digitally signs an X.509 certificate containing the owner's public key. Modern operating systems and browsers ship with a pre-installed Root CA Trust Store. When connecting to a website, the browser validates the cryptographic certificate chain from the leaf certificate up to a trusted root CA.

Technical Example & Practical Implementation

X.509 Certificate Trust Chain Verification

The three-tier hierarchical validation structure of internet PKI

Root CA (e.g., DigiCert Global Root G2)
├── Built directly into OS / Browser Trust Store
└── Digitally signs Intermediate CA
    │
    └── Intermediate CA (e.g., DigiCert TLS RSA SHA256 2020 CA1)
        ├── Acts as operational buffer for the offline Root
        └── Digitally signs Leaf Certificate
            │
            └── Leaf Certificate (e.g., *.curious-techie.com)
                ├── Subject: CN=curious-techie.com
                ├── Public Key: 2048-bit RSA / 256-bit ECDSA
                └── Validates server identity during TLS handshake