IP address 84.201.20.74
Last confirmed 2026-09-10, first seen 2026-08-31. On AS214036.
This address answered on 3 ports — :443, :56002, :56001.
84.201.20.74:443 · PureRAT
Last confirmed (5 days ago)
The certificate names above are what the certificate ASSERTS, not proof this host owns them — a self-signed certificate can claim any subject, so treat a familiar name here as an impersonation attempt rather than an identity.
The payload hash is the SHA-256 of the file this listener served when it was scanned. A host can change what it serves at any time, so this identifies a sample to look up or analyse rather than describing what it serves now. Only the response’s Content-Type claimed a download — no executable magic bytes were seen — so the bytes behind this hash are unverified.
84.201.20.74:56002 · PureRAT
Last confirmed (6 days ago)
The certificate names above are what the certificate ASSERTS, not proof this host owns them — a self-signed certificate can claim any subject, so treat a familiar name here as an impersonation attempt rather than an identity.
84.201.20.74:56001 · PureRAT
Last confirmed (6 days ago)
The certificate names above are what the certificate ASSERTS, not proof this host owns them — a self-signed certificate can claim any subject, so treat a familiar name here as an impersonation attempt rather than an identity.
Observation history
Observed on 11 of the 18 days since this archive began recording, 2026-08-29 UTC. Presence is per UTC day: a day is marked when the scanner confirmed this address at least once, not once per scan.
Shared JA4X issuance template · 67 hosts
These hosts issued certificates from the same template — the same distinguished-name fields hashed in the same order. It links tooling, not necessarily an operator.
Showing 24 of 67. The rest are reachable from any of them.
Pivots & lookups
Listed in error?
This page is generated from automated scanning and is publicly available. If you are responsible for this address and it should not be listed, write to support@publicmosaic.com — see abuse & takedown for what we need and what happens next, or opt-out to exclude a whole range from scanning.
Addresses are frequently compromised third-party hosts rather than infrastructure their owner stood up. A listing records what a scan observed at a point in time; it is not an allegation about whoever pays for the address.