Statistics

WR2

URLs
9
Brands targeted
4
Unique IPs
6

What is WR2?

Google Trust Services LLC RSA since 2023 chains to GTS Root R1

RSA DV TLS for sites that still need RSA chains (legacy clients, certain enterprise middleboxes) and for Google properties that pin RSA. The RSA counterpart to WE1/WE2. Same operator, same ACME endpoint, same abuse profile.

Suspicious sites — confidence is not always 100%. Use for Threat Hunting or watchlists.

Last check (UTC) First seen (UTC) URL Screenshot Flags Details
2026-06-05 01:30 2026-06-03 08:00
https://60f62645a8a2915.content-storage-download.googleapis.com/b04a9…
Screenshot of 60f62645a8a2915.content-storage-download.googleapis.com TweetFeed Details
2026-06-05 01:30 2026-04-25 01:01
https://metamaskwallett.blogspot.com
Screenshot of metamaskwallett.blogspot.com OpenPhish urlscan Details
2026-06-05 01:30 2026-04-24 13:03
https://instagram-analytics.blogspot.com
Screenshot of instagram-analytics.blogspot.com OpenPhish Details
2026-06-05 01:30 2026-04-20 13:01
http://instagramusicabrasilinstagram.blogspot.com
Screenshot of instagramusicabrasilinstagram.blogspot.com OpenPhish Details
2026-06-05 01:30 2026-04-20 13:01
https://instagramusicabrasilinstagram.blogspot.com
Screenshot of instagramusicabrasilinstagram.blogspot.com OpenPhish Details
2026-06-05 01:30 2026-04-16 13:02
http://login-facebookaccount.blogspot.com
Screenshot of login-facebookaccount.blogspot.com OpenPhish urlscan Details
2026-06-05 01:30 2026-04-15 13:05
http://barcelona-facebook.blogspot.com
Screenshot of barcelona-facebook.blogspot.com OpenPhish Details
2026-06-05 01:30 2026-04-15 13:05
http://metamaskwallett.blogspot.com
Screenshot of metamaskwallett.blogspot.com OpenPhish Details
2026-06-05 01:30 2026-04-15 01:01
http://facebooktechnicalsupportnumber123.blogspot.com
Screenshot of facebooktechnicalsupportnumber123.blogspot.com OpenPhish urlscan Details

Suspicious sites — confidence is not always 100%. Use for Threat Hunting or watchlists.

URL Screenshot Flags Details
https://60f62645a8a2915.conte… Screenshot of 60f62645a8a2915.content-storage-download.googleapis.com TweetFeed Details
https://metamaskwallett.blogs… Screenshot of metamaskwallett.blogspot.com OpenPhish urlscan Details
https://instagram-analytics.b… Screenshot of instagram-analytics.blogspot.com OpenPhish Details
http://instagramusicabrasilin… Screenshot of instagramusicabrasilinstagram.blogspot.com OpenPhish Details
https://instagramusicabrasili… Screenshot of instagramusicabrasilinstagram.blogspot.com OpenPhish Details
http://login-facebookaccount.… Screenshot of login-facebookaccount.blogspot.com OpenPhish urlscan Details
http://barcelona-facebook.blo… Screenshot of barcelona-facebook.blogspot.com OpenPhish Details
http://metamaskwallett.blogsp… Screenshot of metamaskwallett.blogspot.com OpenPhish Details
http://facebooktechnicalsuppo… Screenshot of facebooktechnicalsupportnumber123.blogspot.com OpenPhish urlscan Details

Brands most often impersonated with WR2

Among the active sites currently using a WR2 certificate, these are the brands attackers are mimicking most:

Frequently asked questions about WR2

What is WR2?

WR2 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; WR2 as a CA is fine.

Is WR2 a legitimate certificate authority?

Yes. WR2 is a publicly trusted intermediate CA operated by Google Trust Services LLC, 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; WR2 keeps signing millions of legitimate sites.

Who runs the WR2 certificate authority?

WR2 is operated by Google Trust Services LLC. It is a RSA intermediate that chains up to the GTS Root R1 root, which Google Trust Services LLC 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 WR2 mean when my browser shows it as the issuer?

When a browser shows WR2 as the certificate issuer for a site, it means TLS was validated through Google Trust Services LLC's RSA chain ending at GTS Root R1. That is normal for tens of millions of legitimate sites that use Google Trust Services LLC'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 WR2 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 WR2 itself.

How do I verify a certificate issued by WR2?

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 WR2 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 WR2 and WE1?

WR2 and its siblings (WE1, WE2, WR1, GTS CA 1C3) 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.