# 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:
- ASN: 55836 (IRT-RELIANCEJIO-IN)
- Organization: Reliance Jio Infocomm Ltd.
- Location: Mumbai, Maharashtra, India (IN)
- RIR: ARIN
Service Configuration:
- Open Ports: TCP/80 (HTTP), TCP/443 (HTTPS)
- Server Fingerprint: Apache/2.2.15 (CentOS)
- TLS Certificate: Self-signed SonicWALL management certificate (CN=192.168.168.168)
- Connection Type: Mobile (LTE/5G via Jio network)
Network Stability:
- Control Plane Status: Unstable routing
- Operator Score: 0.2174 (Minimal)
- Threat Persistence: 0 days observed
- Ownership Changes: 0
---
## Threat Indicators
Blacklist Presence:
- DNSBL Listed: 3 of 8 total lists
- Max Severity: High
- Recent Listings: 4 of 8 lists (observed 2026-06-22)
Network Behavior:
- HTTP/HTTPS signals detected with 302 redirects
- Robots.txt: Full site disallow (`User-agent: * Disallow: /`)
- Response Time: 937ms (elevated latency)
- X-Frame-Options: SAMEORIGIN
Campaign Association:
- Known Campaigns: None identified
- Cert Matches: 0
- Correlated IPs: 0
---
## Neighborhood Analysis
Subnet: 136.232.11.10/24
- Abuse Density: 0 (mostly clean)
- Risk Distribution: No high/medium-risk siblings identified
- Active Siblings: 1
- Inherited Risk: 2
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:
- 2026-06-22: Blacklist listings (4 of 8 lists, high severity)
- 2026-06-21: Blacklist listings (3 of 8 lists, high severity)
- 2026-06-20: HTTP/HTTPS service detection
- Threat Persistence Days: 0
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:
- Network: RELIANCEJIO-IN (dominant relationship type)
- Multiple Same Network references indicating cluster activity within Reliance Jio infrastructure
---
## 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:
- High risk score (80/100)
- Multiple blacklist listings with high severity
- Mobile carrier association with known infrastructure
- Self-signed certificate indicating potential tunneling or C2 infrastructure
Mitigating Factors:
- Minimal neighborhood abuse density
- No persistent malicious behavior detected
- Single threat observation count
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.
๐ข Ownership & Registration
| Organization | IRT-RELIANCEJIO-IN |
| ASN | AS55836 |
| Network Name | โ |
| CIDR Block | โ |
| RIR | ARIN |
| Country | โ |
| Abuse Contact | Available via RDAP |
๐ DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No โ PTR hostname does not resolve back to this IP (weak signal) |
๐ DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Present |
โ๏ธ Network Classification
| Infrastructure | Mobile |
| Service Purpose | Web Server |
| Network Tier | Unknown โ Insufficient routing data to classify |
๐ Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | โ |
| 443 | https | tcp | โ |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | Apache/2.2.15 (CentOS) |
| HTTP Title | โ |
๐ TLS Certificate
| SANs | None |
| Valid From | 1970-01-01T00:00:01+00:00 |
| Valid Until | 2038-01-19T03:14:07+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 24855 days |
| Serial Number | 1B760C7A15F000915BDE54005E4B6FDA21B42A14 |
| Thumbprint | 9FE9E05BCAE4BBD7C4B6B557647935E02CC2A7E4 |
๐ฏ Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 29% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 28% | 2 | 4 |
| ownership | 20% | 2 | 3 |
| reputation | 21% | 1 | 3 |
| geolocation | 30% | 2 | 3 |
| Overall | 23% | 10 | 18 |
| Data Coherence | Mixed Signals (68%) โ 2 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
โ TLS certificate claims US but primary geo says IN
๐ Observation Timeline ๐ Fresh
| First Seen | 2026-05-07 23:03:40 UTC |
| Last Seen | 2026-06-26 18:10:36 UTC |
| Profile Built | 2026-06-26 21:39:08 UTC |
| Data Freshness | Fresh |
| Signal Types | 25 |
| Total Observations | 26 |
Full dossier details are available via our API.