31.129.107.245
Intelligence Briefing: 31.129.107.245/32
Ownership and Geolocation:
The IP address is assigned to ASN 198610 (BEGET-MNT) under the organization RU-BEGET. Geolocation data identifies the location as St Petersburg, RU, with a consensus accuracy radius of 5000 km.
Risk and Threat Assessment:
Current reputation is Moderate Risk with a risk score of 40. No known campaigns, Tor exit nodes, or known attacker indicators were detected. The address is listed on 2 DNSBL entries out of 8 total checks, yet no specific threat feed indicators were recorded.
Network Behavior and Services:
Active services were not detected; the service purpose is listed as Firewalled / No Services. No open ports, TLS certificates, or HTTP banners were observed. DNSSEC validation is valid, while route stability is flagged as false despite zero route changes in the last 30 days.
Summary:
The address represents a passive, firewalled endpoint within a Russian hosting infrastructure with moderate risk scoring due to minor DNSBL listings.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | BEGET-MNT |
| ASN | AS198610 |
| Network Name | RU-BEGET |
| CIDR Block | 31.129.96.0/20 |
| RIR | RIPE |
| Country | RU |
| 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 | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS198610 |
| Network Prefix | 31.129.107.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 12% | 3 | 3 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-02 04:21:46 UTC |
| Last Seen | 2026-08-25 06:06:28 UTC |
| Profile Built | 2026-08-29 09:08:14 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 20 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 31.129.107.245
Who owns the IP address 31.129.107.245?
31.129.107.245 is registered to BEGET-MNT. The address falls within the 31.129.96.0/20 network block. Registration is held at RIPE.
Where is 31.129.107.245 located?
Geolocation data places 31.129.107.245 in St Petersburg, St.-Petersburg, Russia. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 31.129.107.245 malicious or safe?
31.129.107.245 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.