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.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- 31.135.66.178
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-08-24 20:03 UTC
- Forward DNS last checked
- 2026-08-24 20:03 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 31.135.66.178
- CIDR range
- 31.135.64.0/20
- IP range (int)
- 528,957,440 — 528,961,535
- Prefix length
- /20
- Organization
- Intek-M LLC
- ASN
- AS43865
- ASN name
- Intek-M LLC
- Location
- Moscow, Moscow, Russia
- Coordinates
- 55.748700, 37.618700
- Accuracy radius
- 10 km
- Postal code
- 101000
- Regional Internet Registry
- RIPE
- Allocated
- 2011-06-24
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-08-23 05:21: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 31.135.66.178?
31.135.66.178 is allocated to Intek-M LLC (AS43865), registered in Moscow, Russia.
Where is 31.135.66.178 located?
The geolocation for 31.135.66.178 maps to Moscow, Russia 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.135.66.178 on?
31.135.66.178 belongs to the 31.135.64.0/20 network block announced by AS43865. This range contains 4,096 addresses.
Does 31.135.66.178 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.
