IP Report

138.124.123.52

AEZA INTERNATIONAL LTD · AS210644 · Charlotte (Oakview Terrace), United States

45/100
Low risk
0–1920–4950–7980–100

Score 45 of 100, in the low risk band. Bands run 0 to 19 minimal, 20 to 49 low, 50 to 79 medium, 80 to 100 high.

Its risk score of 45/100 is low-to-moderate: some signal is present, but on its own it would not justify blocking a visitor.

Detection signals

Anonymity signals— act on these
VPN infrastructure
Inferred from ASN / hosting pattern
0.60
Medium
Infrastructure facts— context, not accusations
Datacenter
Listed in a published datacenter range feed
Hosting network
ASN classification

Not detected: Tor, Proxy, Crawler

Summary

138.124.123.52 is part of a VPN service's infrastructure. Visitors arriving from it are relaying their traffic through the service, so the address says where the tunnel ends, not where the person is.

The address is announced by AEZA INTERNATIONAL LTD (AS210644) and geolocates to Charlotte (Oakview Terrace), North Carolina, United States.

Why this address scores 45

It falls within IP ranges operated by VPN providers, so the address conceals where its traffic really originates.

It sits in datacenter address space, where automated traffic vastly outnumbers human visitors.

Individually these are weak signals; together they lift the score to 45/100, which is enough to be worth noting but not enough to act on by itself.

Observation history

This address has been looked up through Predax once, on September 3, 2026.

Network & location

ASN
AS210644
Country
United States (US)
Provider
AEZA INTERNATIONAL LTD
Region
North Carolina
CIDR
138.124.123.0/23
City
Charlotte (Oakview Terrace)
Network type
hosting
PTR
tranquilchurch.ptr.network
First seen
9/3/2026, 5:50:11 AM
Last seen
9/3/2026, 5:50:11 AM
Times seen
1

What to do with this

If you run a site and this address showed up

Blocking VPN and proxy addresses outright also blocks real customers who use privacy tools every day.

If a visitor from this address disputes a block, look at what they did — the request pattern — rather than where they came from. Unblocking a disputed VPN address is usually the right call unless the behaviour itself was abusive.

If you found this address in your logs

The real client behind this address is elsewhere; geolocation and per-IP identity are both misleading for it.

Expect many unrelated users to share this address over time. Rate limits keyed on it will throttle strangers together, so prefer account- or token-level limits for anything that matters.

Loading map...

Detection sources

  • VPNMedium · 60%

    Inferred from ASN / hosting pattern. Traffic from a VPN exit. Could be a privacy-conscious user, or an adversary using a VPN to evade rate limits — context matters.

Check Another IP