Amazon RSA 2048 M04
What is Amazon RSA 2048 M04?
Fourth ACM public-certificate intermediate, rotated alongside M01-M03. Functionally identical to its M0x siblings; AWS load-balances issuance across the rotation.
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 07:30 | 2026-06-03 01:01 |  |
OpenPhish | Details | |
| 2026-06-04 07:30 | 2026-06-03 01:01 |  |
OpenPhish | Details |
Brands most often impersonated with Amazon RSA 2048 M04
Among the active sites currently using a Amazon RSA 2048 M04 certificate, these are the brands attackers are mimicking most:
- Amazon (2 sites)
Frequently asked questions about Amazon RSA 2048 M04
What is Amazon RSA 2048 M04?
Amazon RSA 2048 M04 is a publicly trusted intermediate certificate authority operated by Amazon Trust Services LLC and chained to Amazon Root CA 1. 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; Amazon RSA 2048 M04 as a CA is fine.
Is Amazon RSA 2048 M04 a legitimate certificate authority?
Yes. Amazon RSA 2048 M04 is a publicly trusted intermediate CA operated by Amazon 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; Amazon RSA 2048 M04 keeps signing millions of legitimate sites.
Who runs the Amazon RSA 2048 M04 certificate authority?
Amazon RSA 2048 M04 is operated by Amazon Trust Services LLC. It is a RSA intermediate that chains up to the Amazon Root CA 1 root, which Amazon 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 Amazon RSA 2048 M04 mean when my browser shows it as the issuer?
When a browser shows Amazon RSA 2048 M04 as the certificate issuer for a site, it means TLS was validated through Amazon Trust Services LLC's RSA chain ending at Amazon Root CA 1. That is normal for tens of millions of legitimate sites that use Amazon 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 Amazon RSA 2048 M04 show up on phishing sites?
Amazon 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 Amazon RSA 2048 M04 itself.
How do I verify a certificate issued by Amazon RSA 2048 M04?
In a desktop browser, click the padlock in the address bar and open the certificate viewer. Confirm the issuer chain ends at Amazon Root CA 1, that the subject matches the domain you expect, and that the notAfter date has not passed. A valid Amazon RSA 2048 M04 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 Amazon RSA 2048 M04 and Amazon RSA 2048 M01?
Amazon RSA 2048 M04 and its siblings (Amazon RSA 2048 M01, Amazon RSA 2048 M02, Amazon RSA 2048 M03) share the same operator (Amazon Trust Services LLC) and roll up to the same root (Amazon Root CA 1). 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.