ProteQC flags hidden certificate risk before March 2027 changes
ProteQC says upcoming certificate rules could trigger renewal failures and expose weak CAA configurations before a March 15, 2027 deadline. The firm has launched a free checker to help organisations spot problems as public TLS certificates move to shorter lifetimes and validation rules tighten.
Why it matters: - New certificate rules taking effect on March 15, 2027 could disrupt renewals for organisations that have not updated their domain and certificate controls. - Public TLS certificates will move to a maximum 100-day lifetime for newly issued certificates, raising the stakes for automation and accurate configuration. - Domain-validation evidence older than 100 days will no longer be reusable, making renewal processes more frequent and more operationally sensitive. - Organisations that need to control which certificate authorities issue their certificates may be the most exposed if their CAA records are missing the new RFC 8657 parameters.
What happened: - ProteQC, an independent post-quantum cryptography advisory firm, published new research on October 7, 2026 warning of a certificate security risk ahead of the March 2027 deadline. - The firm says many publicly trusted certificate authorities will need to process additional Certificate Authority Authorization parameters beginning March 15, 2027. - ProteQC also launched a free browser-based CAA checker to help organisations review their current configuration before the deadline.
The details: - ProteQC’s analysis of popular websites found the new RFC 8657 CAA controls were almost entirely absent. - The main concern is not that existing CAA records will break, but that organisations may be forced to adopt the new control under deadline pressure for the first time. - ProteQC reviewed guidance from NCSC, CISA, ENISA, BSI and ANSSI and found no dedicated national-agency advisory, as of September 29, 2026, that specifically names the March 2027 RFC 8657 processing deadline or the 100-day validation-reuse limit. - The company said certificate lifecycle changes have been widely discussed in the PKI industry, but the combined operational impact deserves broader attention. - ProteQC recommends organisations inventory all publicly trusted certificates and domains, name owners, automate issuance and validation, and treat domain validation as a recurring process. - The company’s checklist also advises auditing CAA records for RFC 8657 parameters, applying them consistently to standard and wildcard issuance, or removing them and testing against a CA that already enforces them. - The free client-side check at ProteQC’s CAA checker shows a domain’s current position in seconds and sends nothing to ProteQC; the public DNS resolver sees the query. - Organisations are also urged to treat domain validation as a quarterly control rather than an annual event.
Between the lines: - ProteQC is framing the March 2027 changes as a broader readiness test, not just a compliance update. - The new certificate rules may expose organisations that lack clear ownership of cryptographic assets or do not have automated renewal workflows. - The timing matters because the most common failure mode may be operational, not technical: teams could discover missing controls only when renewals are already due. - ProteQC says the same skills needed for certificate management will also matter for post-quantum cryptography migration. - The company argues that organisations that can inventory assets, assign ownership and respond quickly to standards changes will be better positioned for the quantum transition.
What’s next: - Organisations have until March 15, 2027 to review CAA records, fix validation workflows and automate certificate renewal. - ProteQC says teams should use the deadline to strengthen broader certificate management practices before the shorter certificate lifecycle takes effect. - The firm expects the operational lessons from this deadline to carry over into future post-quantum cryptography migrations.
The bottom line: - The March 2027 certificate changes could turn a background IT function into a near-term operational risk for organisations that are not ready.
Disclaimer: This article was produced by AGP Wire with the assistance of artificial intelligence based on original source content and has been refined to improve clarity, structure, and readability. This content is provided on an “as is” basis. While care has been taken in its preparation, it may contain inaccuracies or omissions, and readers should consult the original source and independently verify key information where appropriate. This content is for informational purposes only and does not constitute legal, financial, investment, or other professional advice.
Sign up for:
Cryptocurrency Insider Today
The daily local news briefing you can trust. Every day. Subscribe now.
Check Your Email!
We sent a one-time activation link to: .
Confirm it's you by clicking the email link.
If the email is not in your inbox, check spam or try again.
Welcome back!
is already signed up. Check your inbox for updates.