IPDebrief

188.143.232.243

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# INTELLIGENCE BRIEFING: 188.143.232.243/32

## EXECUTIVE SUMMARY

IP 188.143.232.243 is a Russian-origin address with a moderate risk score of 40. The address resides within a high-abuse subnet (188.143.232.0/24) showing 0.7812 abuse density with 200 threat-sibling IPs. Current profile indicates no active threat indicators, but the network context and historical signals warrant defensive monitoring.

## OWNERSHIP & GEOLOCATION

## RISK ASSESSMENT

MetricValueStatus
Overall Risk Score40Moderate
Operator Score0.2174Minimal
Abuse ConfidenceN/ANot Available
DNSBL Listed1/8 listsFlagged
ISP ClassificationProvider/InfrastructureNot Residential

## THREAT INDICATORS

## NETWORK BEHAVIOR

## NEIGHBORHOOD ANALYSIS (188.143.232.0/24)

The subnet demonstrates significant malicious activity with 78% of active IPs classified as threats. This contextual risk factor elevates the threat posture for this address.

## OBSERVATION HISTORY

Historical data indicates no escalating threat behavior, though DNSBL listing persists across 8 lists.

## RECOMMENDED ACTIONS

Immediate Mitigation

Block the address at network perimeter and application layers:

iptables:

```

iptables -A INPUT -s 188.143.232.243 -j DROP

```

nftables:

```

nft add rule inet filter input ip saddr 188.143.232.243 drop

```

nginx:

```

deny 188.143.232.243;

```

pfSense:

```

188.143.232.243/32

```

Cloudflare WAF:

```json

{"description":"Block 188.143.232.243 β€” IPDebrief risk score 40","action":"block","filter":{"expression":"ip.src eq 188.143.232.243"}}

```

AWS WAF:

```json

{"Addresses":["188.143.232.243/32"],"Description":"IPDebrief risk 40"}

```

## SOC RECOMMENDATIONS

1. Block the IP at edge firewall and WAF levels

2. Monitor for lateral connections to related IPs in 188.143.232.0/24

3. Review logs for any inbound connections from this subnet

4. Update threat intelligence feeds with ASN 34665 if not already present

5. Consider blocking the entire /24 subnet given the 0.7812 abuse density

## CONCLUSION

While the individual IP shows no active malicious indicators, the high-abuse subnet context and DNSBL listings justify defensive blocking. The address is best classified as "moderate risk due to network association" requiring perimeter filtering.

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
22%
24
routing
13%
11
services
20%
23
ownership
20%
23
reputation
19%
13
geolocation
27%
23
Overall20%1017
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-24 04:01:36 UTC
Data FreshnessLive
Signal Types25
Total Observations26
πŸ” 25 signal types Β· 26 observations collected
This report is generated from 25+ 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.