# IPDEBRIEF INTELLIGENCE BRIEFING
Target: 82.202.131.224/32
Classification: LOW RISK
Date: 2026-07-27
---
## EXECUTIVE SUMMARY
IP address 82.202.131.224 presents a low-risk threat profile (Risk Score: 25) with no active malicious indicators. The address is assigned to BEGET hosting infrastructure in St. Petersburg, Russia, and shows no evidence of abuse, blacklisting, or association with known threat campaigns.
---
## INFRASTRUCTURE PROFILE
| Attribute | Value |
|---|---|
| **ASN** | 198610 |
| **Organization** | BEGET-MNT (RU-BEGET) |
| **CIDR Block** | 82.202.131.0/24 |
| **Country** | Russia (RU) |
| **Region/City** | St. Petersburg, Russia |
| **RIR** | RIPE |
| **Risk Score** | 25/100 |
| **Reputation** | Low Risk |
---
## NETWORK CHARACTERISTICS
Service Status: Firewalled / No Services
- No open ports detected
- No TLS certificates
- No HTTP services
- No PTR record resolution
DNS Status:
- No forward resolution
- No hosted domains
- No email authentication records (SPF/DMARC)
---
## THREAT INTELLIGENCE
Active Indicators: None
- Blacklist Count: 0
- Known Campaigns: None
- Is Tor Exit Node: No
- Is Known Attacker: No
- Is Spam Source: No
Control Plane:
- BGP Prefix: 82.202.128.0/22
- Route Stability: Unstable (isRouteStable: false)
- DNSBL Listed: 1 of 8 total lists
- RPKI State: Not evaluated
- IRR Consistency: Not evaluated
---
## NEIGHBORHOOD ANALYSIS
Subnet: 82.202.131.0/24
- Abuse Density: 0%
- Classification: Clean
- Active Siblings: 0
- Threat Siblings: 0
- Total Siblings: 1
Assessment: The /24 subnet shows no abuse activity, indicating this IP is not part of a compromised or misconfigured neighborhood.
---
## OBSERVATION HISTORY
Total Observations: 13
Most Recent: 2026-07-27T04:31:55 UTC
Threat Persistence: 0 days
Ownership Changes: 0
Recent Signal Types:
- Subnet classification (confidence: 0.40)
- Network role (confidence: 0.30)
- Ownership data (confidence: 0.90)
- Geolocation (confidence: 0.95)
- Network tracing (confidence: 0.50)
Trend Assessment: No escalation in threat indicators. Historical data shows consistent benign classification.
---
## RELATIONSHIP GRAPH
Total Relationships: 3
- All relationships map to same network: RU-BEGET
- No external associations to hostnames, certificates, or organizations
---
## GEOVALIDATION
Geo Plausibility: True
Distance Validation: 1,672.5 km from probe origin
Minimum Possible RTT: 33.4 ms
Validation Status: ICMP blocked - unable to validate
---
## RECOMMENDED ACTIONS
Firewall/Security Recommendations:
- No immediate blocking required based on current risk profile
- Monitor for service changes if previously firewalled
- Consider geo-blocking if traffic policy requires
SOC Analyst Notes:
- IP demonstrates stable, non-malicious behavior
- No correlation with known threat campaigns
- Clean neighborhood profile supports continued observation
- Low confidence signals suggest limited probe coverage
---
END OF BRIEFING
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 | 82.202.131.0/24 |
| 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 | 82.202.131.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 0% | 0 | 0 |
| routing | 0% | 0 | 0 |
| services | 0% | 0 | 0 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 4% | 1 | 1 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-12 21:07:15 UTC |
| Last Seen | 2026-07-27 04:27:12 UTC |
| Profile Built | 2026-08-30 20:53:28 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 19 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 82.202.131.224
Who owns the IP address 82.202.131.224?
82.202.131.224 is registered to BEGET-MNT. The address falls within the 82.202.131.0/24 network block. Registration is held at RIPE.
Where is 82.202.131.224 located?
Geolocation data places 82.202.131.224 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 82.202.131.224 malicious or safe?
82.202.131.224 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.