server name
blog.naver.com
Too few observations
Too little traffic to read — a spread of 1.0 over three connections is noise; the same over sixty thousand is worth a look.
- domain
Read
client diversity
2 distinct client stacks reach this name.
concentration
0.918 traffic splits near-evenly across many unrelated stacks.
Spread is entropy over the fingerprints reaching this domain, not over the domains a fingerprint reaches. It can’t distinguish one scraper from many people — it measures the mix of software, not who runs it.
Footprint
3
observations
2
distinct clients
2026-07-19
first seen
2026-07-23
last seen
Client stacks reaching this name
- Go net/httpmulti-build67%
- Node.js https / axios / got (no ALPN)multi-build33%
Busiest 2 client stacks on this page. Share is the fraction of this name’s observations. Many distinct fingerprints on a low-traffic name is itself worth a look; a blank JA3 is a permuting client — open the fingerprint for its variants.
| client | JA3 | stability | count | share | first seen | last seen |
|---|---|---|---|---|---|---|
| Go net/http Go 1.21–1.23, static build (CGO off) — distroless/scratch; a different cipher set | — | multi-build | 2 | 67% | 2026-07-20 | 2026-07-23 |
| Node.js https / axios / got (no ALPN) Node 22 — bundled OpenSSL 3 (newer) | — | multi-build | 1 | 33% | 2026-07-19 | 2026-07-19 |