31.192.254.116
31.192.254.116 is an IPv4 address operated by ELCAT-RIPE-MNT (AS42837), geolocated to Bishkek, Kyrgyzstan. Its reverse DNS name is 31-192-254-116.elcat.kg. As of November 6, 2026, IPDebrief rates it High Risk (70/100); no anonymizing service was detected.
The IP address 31.192.254.116/32 was classified as high risk with a risk score of 70. Ownership records indicated association with ASN 42837, ELCAT-RIPE-MNT, under the netname HOMELINE-KG-NET in Bishkek, Kyrgyzstan. Network scans confirmed the address was firewalled with no active services. Despite the lack of open ports, the address was correlated with 12 other IPs within campaign infrastructure and assigned a high likelihood of malicious activity. The address appeared in two DNS blacklists. Recommendations indicated a critical severity action to block the source, citing a high risk score with strong threat evidence. DNS hygiene was rated fair, with SPF and DMARC present but lacking DNSSEC and CAA records.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | ELCAT-RIPE-MNT |
| ASN | AS42837 |
| Network Name | HOMELINE-KG-NET |
| CIDR Block | 31.192.254.0/24 |
| RIR | RIPE |
| Country | KG |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | 31-192-254-116.elcat.kg |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 31-192-254-116.elcat.kg |
🔐 DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Single-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| Closed Ports | 22, 25, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS42837 |
| Network Prefix | 31.192.254.0/24 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Not detected |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 43% | 2 | 5 |
| routing | 19% | 1 | 2 |
| services | 27% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 13% | 1 | 1 |
| Overall | 26% | 9 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-10-08 15:51:50 UTC |
| Last Seen | 2026-11-06 20:31:17 UTC |
| Profile Built | 2026-11-06 20:35:03 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 27 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 31.192.254.116
Who owns the IP address 31.192.254.116?
31.192.254.116 is registered to ELCAT-RIPE-MNT. The address falls within the 31.192.254.0/24 network block. Registration is held at RIPE.
Where is 31.192.254.116 located?
Geolocation data places 31.192.254.116 in Bishkek, Bishkek, Kyrgyzstan. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 31.192.254.116 malicious or safe?
31.192.254.116 currently carries a high risk assessment, meaning indicators associated with malicious or abusive activity have been observed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 31.192.254.116?
The reverse DNS (PTR) record for 31.192.254.116 is 31-192-254-116.elcat.kg. This hostname is not forward-confirmed, so it should be treated as a weak signal.
What ports are open on 31.192.254.116?
Responsive ports observed on 31.192.254.116 include 80. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.