Statistics

Cloudflare Inc ECC CA-3

What is Cloudflare Inc ECC CA-3?

Cloudflare, Inc. ECDSA since 2019 chains to Baltimore CyberTrust Root

Automatic TLS for sites proxied through Cloudflare. If the customer does not upload their own cert, Cloudflare issues one from this intermediate. Seen on any Cloudflare-proxied hostname that uses Cloudflare's Universal SSL. Legitimate use is the default case; the CA itself is not a phishing signal.

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 Cloudflare Inc ECC CA-3

What is Cloudflare Inc ECC CA-3?

Cloudflare Inc ECC CA-3 is a publicly trusted intermediate certificate authority operated by Cloudflare, Inc. and chained to Baltimore CyberTrust Root. 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; Cloudflare Inc ECC CA-3 as a CA is fine.

Is Cloudflare Inc ECC CA-3 a legitimate certificate authority?

Yes. Cloudflare Inc ECC CA-3 is a publicly trusted intermediate CA operated by Cloudflare, Inc., 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; Cloudflare Inc ECC CA-3 keeps signing millions of legitimate sites.

Who runs the Cloudflare Inc ECC CA-3 certificate authority?

Cloudflare Inc ECC CA-3 is operated by Cloudflare, Inc.. It is a ECDSA intermediate that chains up to the Baltimore CyberTrust Root root, which Cloudflare, Inc. 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 Cloudflare Inc ECC CA-3 mean when my browser shows it as the issuer?

When a browser shows Cloudflare Inc ECC CA-3 as the certificate issuer for a site, it means TLS was validated through Cloudflare, Inc.'s ECDSA chain ending at Baltimore CyberTrust Root. That is normal for tens of millions of legitimate sites that use Cloudflare, Inc.'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 Cloudflare Inc ECC CA-3 show up on phishing sites?

Cloudflare, Inc. issues ECDSA 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 Cloudflare Inc ECC CA-3 itself.

How do I verify a certificate issued by Cloudflare Inc ECC CA-3?

In a desktop browser, click the padlock in the address bar and open the certificate viewer. Confirm the issuer chain ends at Baltimore CyberTrust Root, that the subject matches the domain you expect, and that the notAfter date has not passed. A valid Cloudflare Inc ECC CA-3 certificate only proves TLS was negotiated correctly — always verify the domain name itself belongs to the service you intended to visit.

Who can I report a suspicious Cloudflare Inc ECC CA-3 certificate to?

Operators accept abuse reports at their public contact addresses. Cloudflare, Inc. publishes a revocation and abuse policy on its website. phishunt continuously submits flagged domains to Google Safe Browsing, OpenPhish, PhishTank, urlscan.io and TweetFeed — which is typically the fastest path to getting the certificate revoked.