TORONTO, Nov. 11, 2026 — Let's Encrypt has confirmed that its production API is now validating domains from six remote network perspectives, completing a rollout it announced on October 15. The change means every domain validation now involves seven validation requests in total, one from the primary datacenter and six from remote perspectives, with issuance proceeding only when the primary server and a quorum of remote perspectives receive the correct challenge response.
The confirmation came in a post to the Let's Encrypt community forum on the evening of November 10, when Let's Encrypt's Phil wrote that the production API is now using a total of six remote network perspectives. Staging moved to six perspectives on October 27, and the production rollout followed on November 10 as planned, with a scheduled maintenance window that day to add the two additional perspectives.
The move is part of a wider shift across the certificate industry. Under the CA/B Forum Baseline Requirements, section 3.2.2.9 on Multi-Perspective Issuance Corroboration, certificate authorities must use at least five remote network perspectives, spread across at least two distinct Regional Internet Registry regions, from December 15, 2026. Let's Encrypt's six perspectives put it ahead of that bar before the deadline arrives.
The point of the change is to make domain validation harder to subvert. A single validation request can be intercepted if an attacker can steer traffic for a domain, for example through a BGP hijack. When the same challenge has to be answered correctly from several networks in different regions at the same time, that attack becomes far harder to pull off. More perspectives mean more independent witnesses to the same fact.
For the enterprises that rely on those certificates, the operational question is different. Validation is the certificate authority's job. Knowing which certificates your organisation depends on, where they live, when they expire, and how they will be renewed is yours. That is where most certificate estates still fall short. Certificates issued by Let's Encrypt sit alongside certificates from commercial authorities, internal Microsoft ADCS deployments, and cloud providers, spread across load balancers, APIs, IoT devices, and services nobody has inventoried in years.
"Six perspectives make validation stronger, and that is good news for everyone who depends on the public web PKI," said Sarah Reid of Securetron. "But stronger validation does not fix an estate you cannot see. If a certificate is sitting in a forgotten trust store or on a device nobody owns, no amount of validation hardening will save it when it expires or when its issuer changes its roots. The next test for enterprises is inventory: know every certificate, know where it is trusted, and know what happens when it changes."
Securetron's PKI Trust Manager is built for that test. It continuously discovers certificates, expiring assets, and vulnerabilities across the enterprise, with no blind spots and no spreadsheets, and automates issuance, renewal, and monitoring for the entire certificate lifecycle. It offers a single pane of glass across ADCS, Microsoft Certificate Services, Let's Encrypt, DigiCert, ACME, and more, with full audit trails for every action. A built-in RFC 8555 ACME server with EAB, plus SCEP and EST, means certbot, acme.sh, win-acme, and network devices all enrol automatically, and configurable expiry alerting routes warnings to the right teams before an outage happens.
Its Boltron-AI module adds an intelligent operational layer: it discovers applications and services, profiles their configurations, and generates onboarding runbooks that bring each application under management, turning PKI intelligence into automated workflows. The Community Edition manages up to 500 certificates free, on premises or as a service through PKI Trust Cloud.
The December 15 deadline for multi-perspective issuance corroboration is now five weeks away. Certificate authorities are moving. Enterprises that want to keep pace should use the same window to find out what their own estate actually contains, before the next root removal or validation change finds the gaps for them.
About Securetron:
Securetron builds PKI Trust Manager and PKI Trust Cloud, enterprise certificate lifecycle management platforms that discover, provision, renew, and revoke certificates across hybrid estates, with AI-driven onboarding through Boltron-AI. Securetron also builds AI-FW, a self-hosted AI firewall and governance gateway between AI agents and LLM backends. Learn more at https://securetron.net and https://aifw.io.
Press Contact:
Sarah Reid, Securetron
1 Yonge St, Toronto, ON M5E 1E6, Canada
+1 (438) 927-8036
[email protected]
Let's Encrypt's production API now validates domains from six remote network perspectives. Securetron says the change raises the bar for attackers, and the real work for enterprises is knowing every certificate that depends on it.
Media Contact
- Toronto, Canada
- Securetron
- Sarah Reid
- [email protected]
- +1 (438) 927-8036
- Visit Site