Statistics

WR4

TLS certificate intermediate · suspicious phishing activity

URLs
2
Brands targeted
1
Unique IPs
1

What is WR4?

Operator
Google Trust Services LLC
Chains to
GTS Root R1
Key type
RSA
In use since
2024

Newest RSA DV intermediate in Google's WR series, rotated in alongside WR1 and WR2 to spread issuance load and shorten the per-intermediate validity window.

Same operator, same ACME endpoint and abuse profile as WR1/WR2; expect issuance volume to climb as Google rotates intermediates.

Frequently asked questions

What is WR4?

WR4 is a publicly trusted intermediate certificate authority operated by Google Trust Services LLC and chained to GTS Root R1. 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; WR4 as a CA is fine.

Why does WR4 show up on phishing sites?

Google Trust Services LLC 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 WR4 itself.

How do I verify a certificate issued by WR4?

In a desktop browser, click the padlock in the address bar and open the certificate viewer. Confirm the issuer chain ends at GTS Root R1, that the subject matches the domain you expect, and that the notAfter date has not passed. A valid WR4 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 WR4 and WE1?

WR4 and its siblings (WE1, WE2, WR1, WR2) share the same operator (Google Trust Services LLC) and roll up to the same root (GTS Root R1). 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.

Last check (UTC) First seen (UTC) URL Screenshot Flags Details
2026-05-14 07:30 2026-05-07 13:01
http://fuzzy-netflix-clone.firebaseapp.com
Screenshot of fuzzy-netflix-clone.firebaseapp.com OpenPhish urlscan Details
2026-05-14 07:30 2026-04-28 01:01
http://netflix-clone-fff8b.web.app
Screenshot of netflix-clone-fff8b.web.app OpenPhish urlscan Details
URL Screenshot Flags Details
http://fuzzy-netflix-clone.fi… Screenshot of fuzzy-netflix-clone.firebaseapp.com OpenPhish urlscan Details
http://netflix-clone-fff8b.we… Screenshot of netflix-clone-fff8b.web.app OpenPhish urlscan Details