IPDebrief

188.143.232.196

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: IP 188.143.232.196/32

Source IP Profile Summary:

Observation History:

Relationships and Affiliations:

Neighborhood Data:

Actionable Recommendations:

1. Monitor Traffic: Implement real-time monitoring for traffic originating from 188.143.232.196/32 to quickly identify and respond to potential threats.

2. Block or Filter: Consider adding the IP address to a blocklist or implementing firewall rules to prevent communication with known malicious servers.

3. Analyze Patterns: Use network traffic analysis tools to identify patterns of communication that may indicate command-and-control activity or data exfiltration attempts.

4. Update Defenses: Ensure that all security systems are updated to protect against the latest vulnerabilities exploited by traffic from this IP.

5. Collaborate with Peers: Share findings with other security teams and threat intelligence communities to enhance collective defenses against this threat actor.

This intelligence briefing provides a comprehensive overview of the activities and potential risks associated with IP 188.143.232.196/32, enabling SOC teams to take informed defensive actions.

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.