IP address 107.172.20.215
Observed 2026-06-13 to 2026-06-13 and no longer listed. On AS36352. This is an archived record, kept because an address that was listed stays answerable for having been listed.
107.172.20.215:60000 · Viper
no longer listed Last confirmed
The certificate names above were validated by the issuing authority at issuance. They describe the certificate, not conduct by the names' owner — a legitimately issued certificate can be deployed on a listed host by whoever holds its private key, so treat the name as a pivot to investigate rather than as an attribution.
Observation history
Last confirmed 2026-06-13 00:00 UTC — before this archive began recording daily presence on 2026-08-29. Presence is per UTC day: a day is marked when the scanner confirmed this address at least once, not once per scan.
Shared TLS certificate · 39 hosts
These hosts served the same certificate. That is the strongest link this corpus can draw between two addresses, though it evidences a shared BUILD rather than a shared operator: a leaked or resold profile puts the same certificate in different hands. Full cohort →
Showing 24 of 39. Full cohort →
Shared JA4X issuance template · 44 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. Full cohort →
Showing 24 of 44. Full cohort →
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.