Lucian Constantin
CSO Senior Writer

Expired Google certificate temporarily disrupts Gmail service

news
Apr 6, 20152 mins

Google let a certificate linked to the Gmail SMTP server expire, causing issues for third-party email clients

Google forgot to renew one of its TLS certificates, leading to service disruption Saturday for people using Gmail through third-party email clients.

The problem was fixed in a matter of hours, but should serve as a reminder to online service operators that keeping track of digital certificate expiration dates is important and should be planned for in advance.

Some users reported Saturday on Twitter and other sites that email clients like Microsoft Outlook and OS X Mail were displaying certificate errors when trying to send email messages through smtp.gmail.com.

It seems that it wasn’t the SMTP (Simple Mail Transfer Protocol) server’s certificate that expired, but one higher up in the chain that corresponded to Google Internet Certificate Authority G2 — an intermediate certificate authority operated by Google.

When SSL/TLS certificates are validated by software applications, all certificates they link back to need to be valid as well. In this case the certificate for smtp.gmail.com had been issued by Google Internet Authority G2, which had in turn been issued by GeoTrust Global CA.

According to the Gmail status page, it took Google around two and a half hours to fix the problem, which affected “a majority of users.” The certificate was renewed and is now set to expire on Dec. 31, 2016.

While operators of large online services typically monitor their certificates closely, similar expiration incidents have occurred before and when they do, they can have serious consequences.

In February 2013, an expired certificate issue disrupted the Microsoft Azure service worldwide for around a day. Since Azure is a cloud computing platform, many third-party services relying on it were affected as well.

Lucian Constantin

Lucian Constantin writes about information security, privacy, and data protection for CSO. Before joining CSO in 2019, Lucian was a freelance writer for VICE Motherboard, Security Boulevard, Forbes, and The New Stack. Earlier in his career, he was an information security correspondent for the IDG News Service and Information security news editor for Softpedia.

Before he became a journalist, Lucian worked as a system and network administrator. He enjoys attending security conferences and delving into interesting research papers. He lives and works in Romania.

You can reach him at lucian_constantin@foundryco.com or @lconstantin on X. For encrypted email, his PGP key's fingerprint is: 7A66 4901 5CDA 844E 8C6D 04D5 2BB4 6332 FC52 6D42

More from this author