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
- Not on any threat blocklist +5
- Established allocation (14y) +3
- Trust score 83 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ginan.elkdata.ee
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-09-18 20:34 UTC
- Forward DNS last checked
- 2026-09-18 20:34 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 185.7.252.211
- CIDR range
- 185.7.252.0/22
- IP range (int)
- 3,104,308,224 — 3,104,309,247
- Prefix length
- /22
- Organization
- Elkdata OU
- ASN
- AS61189
- ASN name
- Elkdata OU
- Location
- Estonia
- Coordinates
- 59.000000, 26.000000
- Accuracy radius
- 100 km
- Regional Internet Registry
- RIPE
- Allocated
- 2012-10-25
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-07-11 00:20:37
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 185.7.252.211?
185.7.252.211 is allocated to Elkdata OU (AS61189), registered in Estonia.
Where is 185.7.252.211 located?
The geolocation for 185.7.252.211 maps to Estonia 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 185.7.252.211 on?
185.7.252.211 belongs to the 185.7.252.0/22 network block announced by AS61189. This range contains 1,024 addresses.
Does 185.7.252.211 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.
