WE1
What is WE1?
Automated DV TLS for sites using Google's public ACME endpoint, plus Google's own consumer and workspace domains. ECDSA P-256 intermediate in Google's newer 2023 hierarchy. Free and automated — legitimately used at enormous scale, which is also why phishing kits default to it.
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-04 13:30 | 2026-06-02 13:02 | ![]() |
OpenPhish urlscan | Details | |
| 2026-06-04 13:30 | 2026-06-01 01:00 | ![]() |
OpenPhish urlscan | Details | |
| 2026-06-04 13:30 | 2026-05-29 01:00 | ![]() |
OpenPhish | Details | |
| 2026-06-04 13:30 | 2026-05-19 13:01 | ![]() |
OpenPhish | Details | |
| 2026-06-04 13:30 | 2026-05-19 01:00 | ![]() |
GSB OpenPhish urlscan | Details | |
| 2026-06-04 13:30 | 2026-05-16 01:01 | ![]() |
GSB OpenPhish | Details | |
| 2026-06-04 13:30 | 2026-05-16 01:01 | ![]() |
OpenPhish | Details | |
| 2026-06-04 13:30 | 2026-05-16 01:00 | ![]() |
GSB OpenPhish | Details | |
| 2026-06-04 13:30 | 2026-05-06 13:04 | ![]() |
GSB OpenPhish | Details | |
| 2026-06-04 13:30 | 2026-05-06 13:04 | ![]() |
GSB OpenPhish urlscan | Details | |
| 2026-06-04 13:30 | 2026-05-06 13:04 | ![]() |
GSB OpenPhish urlscan | Details | |
| 2026-06-04 13:30 | 2026-04-29 01:04 | ![]() |
OpenPhish | Details | |
| 2026-06-04 13:30 | 2026-04-13 09:00 | ![]() |
PhishTank | Details | |
| 2026-06-04 13:30 | 2026-03-30 13:01 | ![]() |
GSB OpenPhish urlscan | Details |
Suspicious sites — confidence is not always 100%. Use for Threat Hunting or watchlists.
| URL | Screenshot | Flags | Details |
|---|---|---|---|
| https://santander.kinsta.cloud | ![]() |
OpenPhish urlscan | Details |
| https://stg-santander-santand… | ![]() |
OpenPhish urlscan | Details |
| https://spotifypremiumapkmund… | ![]() |
OpenPhish | Details |
| https://seguridadsocialnotici… | ![]() |
OpenPhish | Details |
| https://facebook-watch.pages.… | ![]() |
GSB OpenPhish urlscan | Details |
| https://meet-googlee463479756… | ![]() |
GSB OpenPhish | Details |
| http://meet-googlee7563454656… | ![]() |
OpenPhish | Details |
| https://meet-googlee782362905… | ![]() |
GSB OpenPhish | Details |
| http://access-learn-kraken-en… | ![]() |
GSB OpenPhish | Details |
| http://welcome-coinbase-logwe… | ![]() |
GSB OpenPhish urlscan | Details |
| http://help-metamaskio-docs.t… | ![]() |
GSB OpenPhish urlscan | Details |
| http://kraken.rs | ![]() |
OpenPhish | Details |
| https://binance-zh.com | ![]() |
PhishTank | Details |
| https://security.email-micros… | ![]() |
GSB OpenPhish urlscan | Details |
Brands most often impersonated with WE1
Among the active sites currently using a WE1 certificate, these are the brands attackers are mimicking most:
- Google (3 sites)
- Banco Santander (2 sites)
- Kraken (2 sites)
- Spotify (1 site)
- Seguridad Social (1 site)
- Facebook (1 site)
Frequently asked questions about WE1
What is WE1?
WE1 is a publicly trusted intermediate certificate authority operated by Google Trust Services LLC and chained to GTS Root R4. 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; WE1 as a CA is fine.
Is WE1 a legitimate certificate authority?
Yes. WE1 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; WE1 keeps signing millions of legitimate sites.
Who runs the WE1 certificate authority?
WE1 is operated by Google Trust Services LLC. It is a ECDSA intermediate that chains up to the GTS Root R4 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 WE1 mean when my browser shows it as the issuer?
When a browser shows WE1 as the certificate issuer for a site, it means TLS was validated through Google Trust Services LLC's ECDSA chain ending at GTS Root R4. 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 WE1 show up on phishing sites?
Google Trust Services LLC 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 WE1 itself.
How do I verify a certificate issued by WE1?
In a desktop browser, click the padlock in the address bar and open the certificate viewer. Confirm the issuer chain ends at GTS Root R4, that the subject matches the domain you expect, and that the notAfter date has not passed. A valid WE1 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 WE1 and WE2?
WE1 and its siblings (WE2, WR1, WR2, GTS CA 1C3) share the same operator (Google Trust Services LLC) and roll up to the same root (GTS Root R4). 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.













