31.59.160.32
IP Intelligence Briefing: 31.59.160.32
Risk Assessment
The IP address 31.59.160.32 was classified as Moderate Risk with a risk score of 40. The address was identified as a Suspicious Host with one threat observation recorded.
Ownership and Infrastructure
The endpoint belonged to ASN 203861 (GOLD-MNT / Miteflux) under the RIPE region. Geolocation data presented a contradiction between Stockholm, Sweden, and Iran. The network role was categorized as a Web Server, though cloud and CDN indicators were absent.
Technical Configuration
The host operated nginx/1.22.1 on ports 80 (HTTP), 443 (HTTPS), and 22 (SSH). The TLS certificate subject was proxy.stresser.es. HTTP requests returned a 502 Bad Gateway status. DNS hygiene was rated Poor, with DNSSEC validation enabled but missing SPF, DM
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | GOLD-MNT |
| ASN | AS203861 |
| Network Name | Miteflux |
| CIDR Block | 31.59.160.0/24 |
| RIR | RIPE |
| Country | SE |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | proxy.stresser.es |
| Valid From | 2026-07-17T23:42:33+00:00 |
| Valid Until | 2026-10-15T23:42:32+00:00 |
🛡️ Public Network Snapshot
| Origin ASN | AS203861 |
| Network Prefix | 31.59.160.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 | 27% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 17% | 2 | 3 |
| ownership | 23% | 2 | 4 |
| reputation | 23% | 1 | 4 |
| geolocation | 12% | 2 | 2 |
| Overall | 18% | 10 | 18 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-10 14:01:59 UTC |
| Last Seen | 2026-09-05 18:13:25 UTC |
| Profile Built | 2026-09-05 18:26:14 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 35 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 31.59.160.32
Who owns the IP address 31.59.160.32?
31.59.160.32 is registered to GOLD-MNT. The address falls within the 31.59.160.0/24 network block. Registration is held at RIPE.
Where is 31.59.160.32 located?
Geolocation data places 31.59.160.32 in London. The local time zone is Europe/Stockholm. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 31.59.160.32 malicious or safe?
31.59.160.32 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 31.59.160.32?
Responsive ports observed on 31.59.160.32 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.