Microsoft Azure TLS Issuing CA 05
What is Microsoft Azure TLS Issuing CA 05?
Earlier-generation Microsoft Azure TLS intermediate, still used on long-lived certificates issued before the 2023 'RSA TLS Issuing CA 0x' rename. Same operator and abuse profile as the newer Azure RSA TLS Issuing CA 03.
Suspicious sites — confidence is not always 100%. Use for Threat Hunting or watchlists.
| Last check (UTC) | First seen (UTC) ▾ | URL | Screenshot | Flags | Details |
|---|
Suspicious sites — confidence is not always 100%. Use for Threat Hunting or watchlists.
| URL | Screenshot | Flags | Details |
|---|
Frequently asked questions about Microsoft Azure TLS Issuing CA 05
What is Microsoft Azure TLS Issuing CA 05?
Microsoft Azure TLS Issuing CA 05 is a publicly trusted intermediate certificate authority operated by Microsoft Corporation and chained to DigiCert Global Root G2. It is recognized by all mainstream browsers and operating system trust stores, so the certificate itself is not a phishing indicator - the same intermediate signs millions of legitimate sites. phishunt only flags the specific domains listed below as suspicious; Microsoft Azure TLS Issuing CA 05 as a CA is fine.
Is Microsoft Azure TLS Issuing CA 05 a legitimate certificate authority?
Yes. Microsoft Azure TLS Issuing CA 05 is a publicly trusted intermediate CA operated by Microsoft Corporation, included in the Microsoft, Apple, Google and Mozilla root trust stores. Every mainstream browser automatically accepts certificates it signs. The intermediate itself is not a phishing signal — what matters is the specific domain. phishunt flags only the suspicious domains listed below; Microsoft Azure TLS Issuing CA 05 keeps signing millions of legitimate sites.
Who runs the Microsoft Azure TLS Issuing CA 05 certificate authority?
Microsoft Azure TLS Issuing CA 05 is operated by Microsoft Corporation. It is a RSA intermediate that chains up to the DigiCert Global Root G2 root, which Microsoft Corporation also owns. Anyone can look up the chain in the public Certificate Transparency logs; the same operator publishes a Certificate Policy / Certification Practice Statement (CP/CPS) describing how issuance and revocation work.
What does Microsoft Azure TLS Issuing CA 05 mean when my browser shows it as the issuer?
When a browser shows Microsoft Azure TLS Issuing CA 05 as the certificate issuer for a site, it means TLS was validated through Microsoft Corporation's RSA chain ending at DigiCert Global Root G2. That is normal for tens of millions of legitimate sites that use Microsoft Corporation's automated DV TLS. The certificate proves the connection is encrypted and that the certificate matches the hostname — it does not prove the site behind it is trustworthy. Always verify the domain name itself.
Why does Microsoft Azure TLS Issuing CA 05 show up on phishing sites?
Microsoft Corporation issues RSA domain-validated certificates automatically and at no cost (or very low cost), which is the exact workflow scammers need to put HTTPS on a throwaway domain. Domain validation only proves that the requester controls the domain name, not that the site behind it is trustworthy. phishunt lists the specific domains currently flagged below — those are the suspicious ones, not Microsoft Azure TLS Issuing CA 05 itself.
How do I verify a certificate issued by Microsoft Azure TLS Issuing CA 05?
In a desktop browser, click the padlock in the address bar and open the certificate viewer. Confirm the issuer chain ends at DigiCert Global Root G2, that the subject matches the domain you expect, and that the notAfter date has not passed. A valid Microsoft Azure TLS Issuing CA 05 certificate only proves TLS was negotiated correctly — always verify the domain name itself belongs to the service you intended to visit.
What is the difference between Microsoft Azure TLS Issuing CA 05 and Microsoft Azure RSA TLS Issuing CA 03?
Microsoft Azure TLS Issuing CA 05 and its siblings (Microsoft Azure RSA TLS Issuing CA 03) share the same operator (Microsoft Corporation) and roll up to the same root (DigiCert Global Root G2). CAs rotate multiple intermediates so that if one key ever has to be revoked, the damage is contained. As a user, you can treat all of them as the same trust anchor.