Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Chrome users do not need to take action to receive Chrome’s protection against certificates identified in the recent .gh, .sl and .as registry hijacks, Google says. The incidents involved attackers changing authoritative DNS records after compromising third-party country-code top-level domain (ccTLD) registries—not a compromise of Google’s own systems. Chrome blocked certificates it identified, while Google also worked with certificate authorities (CAs) to revoke affected certificates for users of other clients.
What happened in the .gh, .sl and .as hijacks?
In an October 6, 2026 incident post, the Chrome Secure Web and Networking Team said it became aware of a series of hijacks affecting the registries for .gh (Ghana), .sl (Sierra Leone) and .as (American Samoa). Attackers changed authoritative DNS records, putting domains in those namespaces at risk and enabling unauthorized HTTPS certificate issuance for several Google properties and domains belonging to other organizations. Google said it had no reason to believe the issuing CAs did anything wrong. Google’s incident account does not establish how many certificates, domains, organizations or users were affected.
How did Chrome and certificate authorities respond?
Chrome blocked unauthorized certificates that Google identified through CRLSets, Chrome’s certificate-revocation mechanism. Google also worked with the issuing CAs to revoke affected certificates, a step intended to help users of other clients as well as Chrome. When Certificate Transparency (CT) log data surfaced additional potentially affected organizations, Chrome proactively blocked more certificates and Google said it contacted affected organizations where possible.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThese safeguards operate at different points: CT monitoring helps domain owners detect unexpected certificate issuance, CA revocation can protect clients that honor the revocation, and Chrome’s certificate blocks provide a browser-side mitigation. None gives every domain owner a complete view of which certificates are authorized for their domains.
#1 Best Overall
What Chrome users should do
Google says Chrome users do not need to take any action to receive the protection from its blocks. If Chrome displays a dangerous-site warning, follow Chrome’s general guidance and do not visit the page; Chrome Help explains how warnings about unsafe sites work. The incident post does not describe a user setting or update that needs to be changed for this response.
What domain owners should do
Monitor CT logs across the whole portfolio
Review CT log entries for unexpected certificate issuance across every domain you operate, including parked domains and regional ccTLD properties. If you control .gh, .sl or .as domains, review recent entries for those names in particular. Monitoring the whole portfolio matters because an unexpected certificate can be issued for a domain that is not part of your main public-facing site.
Rank #2
Restore restrictive CAA controls after DNS control is recovered
Once you have recovered control of authoritative DNS, review your Certification Authority Authorization (CAA) records and restore restrictive policies. Google highlights policies that bind issuance to authorized ACME accounts and permitted validation methods. CAA can limit some future certificate issuance, including issuance that might otherwise rely on cached domain-control-validation state, but it cannot stop issuance while an attacker controls DNS. Treat it as an owner-side control after recovery, not as a defense that neutralizes an active registry or DNS hijack.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What Chrome’s response does—and does not—guarantee
Chrome’s blocks are a mitigation, not a substitute for domain-owner controls. Google cautions that its analysis may not identify every affected domain and that browser-side intervention does not reliably protect users of non-Chrome clients. Owners are best placed to determine which certificates and CAs are authorized for their namespaces, so CT monitoring and sound DNS and CAA practices remain important even when browsers and CAs take action.
Rank #3
- Made in USA - Proudly produced in Ohio by a Veteran-owned business
- Comprehensive Coverage: This BookFactory log book includes essential fields such as post/shift, time of change, date, weather conditions, and a designated space for detailed notes. This ensures that all relevant information is captured and easily accessible.
- Sturdy Cover: The trans-lux cover protects the log book from wear and tear, ensuring its longevity and maintaining the integrity of your recorded data.
- Essential Security Tool: This log book is an indispensable tool for any organization that values security and accountability. It helps to prevent misunderstandings, improve communication, and ensure a smooth transition between shifts.
- Wire-O with Trans-lux cover, 100 Pages, Dimensions 8.5" x 11" - (Security-Pass-Down) Reorder SKU: LOG-100-7CW-PP(Security-Pass-Down)
Google’s incident post reports no numerical total for affected certificates, domains, organizations, users or losses. It also does not establish that every potentially affected certificate or domain has been identified. Avoid treating the published account as a complete inventory of impact.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
