5.196.124.126
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
- Datacenter — common VPN/proxy host −6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (14y) +3
- Trust score 72 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- sam-eu-dev.kibana.pearson.com
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-07-18 22:35 UTC
- Forward DNS last checked
- 2026-07-18 22:35 UTC
Forward DNS records for sam-eu-dev.kibana.pearson.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 103.11.64.116 | — | 172800s |
| A | 103.192.177.10 | — | 172736s |
| A | 103.192.177.68 | — | 172799s |
| A | 104.128.228.101 | — | 172800s |
| A | 104.128.235.103 | — | 172800s |
| A | 104.128.239.17 | — | 172595s |
| A | 141.94.53.215 | — | 172799s |
| A | 157.254.221.234 | — | 172799s |
| A | 157.254.221.243 | — | 172595s |
| A | 178.32.224.222 | — | 172799s |
| A | 185.185.40.126 | — | 172799s |
| A | 185.185.40.18 | — | 172595s |
| A | 185.99.2.43 | — | 172800s |
| A | 185.99.2.53 | — | 172595s |
| A | 193.31.30.152 | — | 172736s |
| A | 193.31.30.61 | — | 172800s |
| A | 208.89.219.137 | — | 172595s |
| A | 210.16.120.28 | — | 172595s |
| A | 210.16.121.100 | — | 172799s |
| A | 212.83.161.171 | — | 172799s |
| A | 216.189.149.40 | — | 172800s |
| A | 216.189.157.109 | — | 172799s |
| A | 23.231.65.42 | — | 172736s |
| A | 37.59.205.12 | — | 172467s |
| A | 37.59.205.2 | — | 172799s |
| A | 45.124.64.113 | — | 172799s |
| A | 45.124.64.76 | — | 172736s |
| A | 45.13.214.144 | — | 172799s |
| A | 45.13.214.180 | — | 172595s |
| A | 45.13.214.88 | — | 172595s |
| A | 45.13.214.89 | — | 172736s |
| A | 45.134.48.44 | — | 172736s |
| A | 45.134.48.48 | — | 172799s |
| A | 45.58.52.118 | — | 172799s |
| A | 45.58.56.7 | — | 172799s |
| A | 5.196.124.126 | — | 172595s |
| A | 5.226.141.216 | — | 172800s |
| A | 77.90.42.46 | — | 172736s |
| A | 80.87.206.53 | — | 172799s |
| A | 85.121.242.133 | — | 172800s |
| A | 85.121.242.134 | — | 172800s |
| A | 85.121.52.213 | — | 172800s |
| A | 85.121.52.66 | — | 172467s |
| A | 85.121.55.217 | — | 172799s |
| A | 85.121.55.246 | — | 172800s |
| A | 89.35.57.20 | — | 172800s |
| A | 89.35.57.21 | — | 172800s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
- sam-eu-dev.kibana.pearson.com stable — Jun 16, 2026 → present
- test.smartconnect-dev.motorolasolutions.com stable — Jun 11, 2026 → Jun 16, 2026
Network Allocation for 5.196.124.126
- CIDR range
- 5.196.124.0/24
- IP range (int)
- 96,762,880 — 96,763,135
- Prefix length
- /24
- Organization
- OVH SAS
- ASN
- AS16276
- ASN name
- OVH SAS
- Location
- France
- Coordinates
- 48.858200, 2.338700
- Accuracy radius
- 500 km
- Regional Internet Registry
- RIPE
- Allocated
- 2012-08-23
- Data source(s)
- ipinfo_lite, maxmind_city, maxmind_country, maxmind_asn
- Last updated
- 2026-07-18 14:05:12
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 5.196.124.126?
5.196.124.126 is allocated to OVH SAS (AS16276), registered in France.
Where is 5.196.124.126 located?
The geolocation for 5.196.124.126 maps to France 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 5.196.124.126 on?
5.196.124.126 belongs to the 5.196.124.0/24 network block announced by AS16276. This range contains 256 addresses.
Does 5.196.124.126 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.
