IPDebrief

82.202.130.248

IP Intelligence Dossier
Your IP: 216.73.216.5
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IPDEBRIEF INTELLIGENCE BRIEFING

Target: 82.202.130.248/32

Date: 2026-07-30

Classification: CLEAN / LOW RISK

---

## EXECUTIVE SUMMARY

IP address 82.202.130.248 is classified as Low Risk with a risk score of 0. The address belongs to BEGET-MNT (AS198610, RU-BEGET) and is geolocated to St. Petersburg, Russia. No threat indicators, blacklists, or malicious activity have been observed. The subnet shows zero abuse density and is classified as clean.

---

## OWNERSHIP & NETWORK CLASSIFICATION

---

## THREAT INDICATORS

Current Status: No active threat indicators detected

---

## NETWORK SERVICES & FINGERPRINTING

---

## NEIGHBORHOOD ANALYSIS (82.202.130.0/24)

The /24 subnet shows no neighboring IPs with elevated risk profiles.

---

## OBSERVATION HISTORY

Total Signals Observed: 16

Recent observations confirm:

---

## RELATIONSHIP GRAPH

Total Relationships: 7 (all to RU-BEGET network)

---

## SECURITY ACTIONS & RECOMMENDATIONS

Recommended Action: No blocking required

---

## CONCLUSION

IP 82.202.130.248 is a low-risk address belonging to a legitimate Russian hosting provider (BEGET). No evidence of malicious activity, scanning, or abuse has been observed. The address and its subnet show clean classification with zero abuse density. No defensive measures are required at this time.

SOC Analyst Guidance: Allow traffic with standard monitoring. No blocking or alerting necessary.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

๐ŸŒ Geolocation

Country๐Ÿ‡ท๐Ÿ‡บ Russia
RegionSt.-Petersburg
CitySt Petersburg
Timezoneโ€”
Latitude59.94
Longitude30.31

๐Ÿข Ownership & Registration

OrganizationBEGET-MNT
ASNAS198610
Network NameRU-BEGET
CIDR Block82.202.130.0/24
RIRRIPE
CountryRU
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo โ€” PTR hostname does not resolve back to this IP (weak signal)

๐Ÿ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown โ€” Insufficient routing data to classify
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverโ€”
HTTP Titleโ€”

๐Ÿ” TLS Certificate

๐Ÿ”’
No certificate
Issued by โ€”
N/A
SANsNone
Valid Fromโ€”
Valid Untilโ€”

๐ŸŽฏ Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
25%
11
routing
25%
11
services
25%
11
ownership
25%
12
reputation
0%
00
geolocation
25%
11
Overall20%56
Coverage: 5/6 dimensions ยท Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-07-28 16:14:46 UTC
Last Seen2026-07-30 18:27:05 UTC
Profile Built2026-07-30 18:37:35 UTC
Data FreshnessLive
Signal Types18
Total Observations18
๐Ÿ” 18 signal types ยท 18 observations collected
This report is generated from 18+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API ๐Ÿ”ง Actions API ๐Ÿ“ง Enterprise Access

โ„น๏ธ About This Report

All data shown is publicly available network metadata โ€” IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.