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
- Long-established allocation (15y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
Reverse-DNS changes between Jun 11, 2026 and Sep 29, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- no PTR — since at least Sep 29, 2026 → present
- gw.cloud.datahata.by stable — Jun 11, 2026 → Sep 29, 2026 1 brief no-PTR dropout
Network Allocation for 31.130.202.113
- CIDR range
- 31.130.202.0/28
- IP range (int)
- 528,665,088 — 528,665,103
- Prefix length
- /28
- Organization
- DataHata Ltd
- ASN
- AS56740
- ASN name
- DataHata Ltd
- Location
- Belarus
- Coordinates
- 53.001100, 28.006500
- Accuracy radius
- 1000 km
- Regional Internet Registry
- RIPE
- Allocated
- 2011-05-06
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-06-09 06:05:50
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 31.130.202.113?
31.130.202.113 is allocated to DataHata Ltd (AS56740), registered in Belarus.
Where is 31.130.202.113 located?
The geolocation for 31.130.202.113 maps to Belarus 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 31.130.202.113 on?
31.130.202.113 belongs to the 31.130.202.0/28 network block announced by AS56740. This range contains 16 addresses.
Does 31.130.202.113 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.
