IPDebrief

136.232.11.10

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.

# IP Intelligence Briefing: 136.232.11.10/32

Classification: High Risk โ€“ Immediate Monitoring Required

---

## Executive Summary

IP 136.232.11.10 is a high-risk address (Risk Score: 80/100) associated with Reliance Jio's mobile network infrastructure in Mumbai, India. The IP exhibits multiple threat indicators including blacklist listings across 3 of 8 monitored feeds and evidence of malicious activity patterns. Immediate defensive actions are recommended.

---

## Technical Profile

Network Attribution:

Service Configuration:

Network Stability:

---

## Threat Indicators

Blacklist Presence:

Network Behavior:

Campaign Association:

---

## Neighborhood Analysis

Subnet: 136.232.11.10/24

The surrounding /24 subnet shows minimal abuse activity, suggesting the threat is isolated to this specific address.

---

## Historical Trend

Observation Count: 26 signals over monitoring period

Key Historical Signals:

The IP shows intermittent blacklist activity with no evidence of persistent malicious behavior over extended periods.

---

## Relationship Graph

Identified Connections: 54 total relationships

Primary Associations:

---

## Recommended Actions

Severity: Critical

Immediate Actions:

1. Firewall Blocking:

- iptables: `iptables -A INPUT -s 136.232.11.10 -j DROP`

- nftables: `nft add rule inet filter input ip saddr 136.232.11.10 drop`

- nginx: `deny 136.232.11.10;`

2. Cloud Security:

- Cloudflare WAF: Block with expression `ip.src eq 136.232.11.10`

- AWS WAF: Add `136.232.11.10/32` to block list

3. Monitoring Enhancement:

- Increase logging verbosity for this IP

- Review all recent activity from this source

- Monitor for lateral movement to related subnet addresses

4. Investigation Priorities:

- Verify if traffic correlates with known malicious campaigns

- Check for certificate-based correlations (self-signed SonicWALL certificate)

- Monitor for new relationships or subnet associations

---

## Risk Assessment

Primary Risk Factors:

Mitigating Factors:

Overall Confidence: Moderate (based on 26 historical observations)

---

*Data Source: IPDebrief Intelligence Platform*

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฎ๐Ÿ‡ณ India
RegionMH
CityMumbai
Timezoneโ€”
Latitude22.00
Longitude79.00

๐Ÿข Ownership & Registration

OrganizationIRT-RELIANCEJIO-IN
ASNAS55836
Network Nameโ€”
CIDR Blockโ€”
RIRARIN
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

InfrastructureMobile
Service PurposeWeb Server
Network TierUnknown โ€” Insufficient routing data to classify
Mobile

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpโ€”
443httpstcpโ€”
Closed Ports22, 25, 3389, 8080, 8443 (2 open / 7 scanned)
ServerApache/2.2.15 (CentOS)
HTTP Titleโ€”

๐Ÿ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
โš ๏ธ
CN=192.168.168.168, OU=HTTPS Management Certificate for SonicWALL (self-signed), O=HTTPS Management Certificate for SonicWALL (self-signed), L=Sunnyvale, S=California, C=US
Issued by CN=192.168.168.168, OU=HTTPS Management Certificate for SonicWALL (self-signed), O=HTTPS Management Certificate for SonicWALL (self-signed), L=Sunnyvale, S=California, C=US
Self-signed: Yes
SANsNone
Valid From1970-01-01T00:00:01+00:00
Valid Until2038-01-19T03:14:07+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period24855 days
Serial Number1B760C7A15F000915BDE54005E4B6FDA21B42A14
Thumbprint9FE9E05BCAE4BBD7C4B6B557647935E02CC2A7E4

๐ŸŽฏ Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
29%
24
routing
13%
11
services
28%
24
ownership
20%
23
reputation
21%
13
geolocation
30%
23
Overall23%1018
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceMixed Signals (68%) โ€” 2 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
โš  Geo sources disagree on country: IN, US
โš  TLS certificate claims US but primary geo says IN

๐Ÿ“… Observation Timeline ๐Ÿ”„ Fresh

First Seen2026-05-07 23:03:40 UTC
Last Seen2026-06-26 18:10:36 UTC
Profile Built2026-06-26 21:39:08 UTC
Data FreshnessFresh
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.