IPDebrief

188.143.232.193

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

# IP Intelligence Briefing: 188.143.232.193/32

Classification: Moderate Risk | Date: 2026-06-18 | Source: IPDebrief Intelligence Platform

## Executive Summary

IP address 188.143.232.193 is associated with Petersburg Internet Network Ltd. (ASN 34665) in St. Petersburg, Russia. The IP presents a moderate risk profile (risk score: 40) with no active threat indicators observed. However, the /24 subnet (188.143.232.0/24) exhibits elevated abuse density (0.7812) with high-abuse classification, warranting defensive monitoring.

---

## Profile & Ownership

AttributeValue
**Risk Score**40 (Moderate)
**ASN**34665 (PINDC-AS)
**Organization**Leon Lundberg / Petersburg Internet Network ltd., RU
**Country/Region**Russia / St. Petersburg
**BGP Prefix**188.143.232.0/23
**DNSSEC**Valid
**CAA Records**Present

---

## Network Classification

The IP is classified as firewalled with no active services detected. Classification flags:

---

## Threat Indicators

Current Status: No active threat indicators

---

## Subnet Neighborhood Analysis

Subnet: 188.143.232.0/24

MetricValue
Abuse Density0.7812 (High Abuse)
Inherited Risk31
Total Siblings256
Active Siblings124
Threat Siblings200
Risk Distribution0 High, 8 Medium, 92 Low

The /24 subnet demonstrates significant abuse prevalence with 200 threat-sibling IPs identified.

---

## Control Plane & Routing

MetricStatus
Route Stable**False**
Route Changes (30d)0
RPKI StateNot Available
IRR ConsistencyNot Available
Operator Score0.2174 (Minimal)
MOASNo

---

## Temporal & Behavioral History

Observation Count: 21 signals over monitoring period

Key Historical Signals:

Behavioral Metrics:

---

## Relationship Graph

Total Relationships: 72

---

## Recommended Actions

Firewall Blocking Rules Available:

```bash

# iptables

iptables -A INPUT -s 188.143.232.193 -j DROP

# nftables

nft add rule inet filter input ip saddr 188.143.232.193 drop

# nginx

deny 188.143.232.193;

# Cloudflare WAF

Filter: ip.src eq 188.143.232.193 (Block)

# AWS WAF

Addresses: 188.143.232.193/32

```

---

## Analyst Notes

1. Subnet Context: Despite moderate IP-level risk score, the /24 subnet shows high abuse density. Consider implementing subnet-level monitoring or blocking rules if the threat surface warrants.

2. No Active Services: The target IP is not hosting detectable services, reducing immediate exploitation risk.

3. Geographic Concentration: All intelligence originates from Russian infrastructure. Coordinate with threat intelligence feeds for regional context.

4. Monitoring Recommendation: Continue passive monitoring. No escalation required at this time, but maintain awareness of subnet-level activity patterns.

5. Action Threshold: Risk score of 40 falls within moderate category. Implement defensive controls based on organizational risk tolerance.

---

*Intelligence generated by IPDebrief Platform. This briefing is based on passive observations and should be validated through additional context before operational deployment.*

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

๐ŸŒ Geolocation

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

๐Ÿข Ownership & Registration

OrganizationLeon Lundberg
ASNAS34665
Network Nameโ€”
CIDR Block188.143.232.0/23
RIRRIPE
Countryโ€”
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 Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

โ˜๏ธ 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%
24
routing
40%
23
services
20%
23
ownership
28%
34
reputation
26%
13
geolocation
28%
23
Overall28%1220
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-07 23:04:48 UTC
Last Seen2026-06-26 18:11:47 UTC
Profile Built2026-06-25 14:03:47 UTC
Data FreshnessLive
Signal Types24
Total Observations26
๐Ÿ” 24 signal types ยท 26 observations collected
This report is generated from 24+ 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.