Update checked October 24, 2026: GoDaddy says some SSL certificates were issued incorrectly, revoked on October 21, and are being reissued. The company warns that affected sites may display browser security warnings or become inaccessible until a replacement certificate is installed. This notice concerns a subset of certificates; GoDaddy has not quantified the affected count in the public help article. Do not assume every GoDaddy customer or every iDvlpr client is affected.
What GoDaddy has confirmed
GoDaddy's help notice says it identified “a number” of incorrectly issued SSL certificates, revoked them on October 21, and is reissuing replacements. A revoked certificate can cause browsers to warn visitors when a domain continues serving that certificate. GoDaddy's notice describes certificate issuance and replacement; it does not say that all GoDaddy websites were breached or that all customer data was exposed.
As of this article's October 24 check, GoDaddy's status page still listed SSL certificates as degraded and the SSL incident as unresolved. The vendor's account page is the source for determining whether a specific certificate needs action. The public notices do not identify every affected hostname, and this article cannot determine whether a particular site is in scope.
On October 24, GoDaddy's public status dashboard marks the SSL Certificates component operational while its incident history continues to show the certificate-replacement notice. That dashboard is useful context, but a component status does not confirm that a particular hostname is serving the correct replacement certificate. Check the certificate attached to the specific domain in the authenticated account and verify what the public site serves.
How to check whether your site needs action
Navigate directly to your GoDaddy account rather than relying on an email link. Open the product page, choose “Manage All” next to SSL Certificates, and inspect the certificate alerts. GoDaddy describes action-required states such as “Install your new certificate,” “We couldn't check your website,” or “This certificate needs your attention.” It also says “No action needed” means no replacement is required for that certificate.
If the account asks you to install a replacement, download the certificate from the authenticated GoDaddy product page and follow the installation instructions for your hosting environment. On shared or managed hosting, the host may install the certificate or need to confirm how it is bound to your domain. On a self-managed server, ask the server administrator to install the correct certificate and chain for each relevant hostname. Do not share a private key in a support ticket or public message.
Verify the public website after replacement
After installation, use GoDaddy's SSL Status Check tool and ask the host to confirm the certificate served by the live website. Check the main domain and any active “www” or subdomain versions separately. Confirm that the browser opens the expected HTTPS URL without a certificate warning and that redirects, contact forms, sign-in pages, and other important customer paths still work.
If a warning remains, do not tell visitors to bypass it. Save the hostname, time, browser message, and certificate details that the host requests, then contact GoDaddy or the hosting provider through its official support route. A certificate can be installed in one place while a proxy, CDN, load balancer, or another hostname still serves a different one. Have the provider identify the endpoint that needs correction.
Who should act, and who should wait?
If GoDaddy's account shows “No action needed” and the live site presents a valid certificate, follow the provider's instructions and avoid unnecessary certificate changes. If you host with a different company, first ask that provider whether the affected certificate or a GoDaddy-issued certificate is part of your setup. Do not replace a certificate just because a headline mentions GoDaddy.
Keep a record of the certificate's hostname, issuer, expiration date, installation location, and renewal owner. Confirm that automatic renewal is functioning where it is configured, and retain a safe recovery procedure. Never disable HTTPS, turn off validation, or send visitors to an insecure version as a workaround.
What this notice does not establish
A certificate replacement notice is not proof that a particular site was compromised. The published GoDaddy notice gives no complete count of affected certificates and does not establish that every GoDaddy service or customer was impacted. Check the provider's account alert and the actual certificate served by your site before drawing conclusions. If your website displays a warning, treat it as an availability and trust issue that needs prompt verification.
For businesses reviewing how their website is built and maintained, see our web design and development services and WordPress support. These services do not replace certificate installation by a hosting provider or qualified server administrator.
This article summarizes provider notices as checked October 24, 2026. Certificate management is environment-specific; use GoDaddy and your host's current instructions for the exact service involved.