Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Forward-confirmed reverse DNS (FCrDNS) +10
- Long-established allocation (17y) +6
- Not on any threat blocklist +5
- Trust score 86 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- 174-126-138-169.cpe.sparklight.net
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 43200 s
- Reverse DNS last checked
- 2026-07-30 16:10 UTC
- Forward DNS last checked
- 2026-07-30 16:10 UTC
Forward DNS records for 174-126-138-169.cpe.sparklight.net
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 174.126.138.169 | — | 172800s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 174.126.138.169
- CIDR range
- 174.126.138.0/24
- IP range (int)
- 2,927,528,448 — 2,927,528,703
- Prefix length
- /24
- Location
- Columbus, Mississippi, United States
- Coordinates
- 33.479600, -88.352800
- Accuracy radius
- 10 km
- Postal code
- 39702
- Regional Internet Registry
- ARIN
- Allocated
- 2009-05-04
- Data source(s)
- maxmind_city, ipinfo_lite, maxmind_country
- Last updated
- 2026-07-28 04:09:03
Frequently Asked Questions
Who owns 174.126.138.169?
174.126.138.169 is allocated to an unknown organization, registered in Columbus, United States.
Where is 174.126.138.169 located?
The geolocation for 174.126.138.169 maps to Columbus, United States based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 174.126.138.169 on?
174.126.138.169 belongs to the 174.126.138.0/24 network block. This range contains 256 addresses.
Does 174.126.138.169 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
