Your IP: 216.73.216.123
๐ค Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 182.79.51.82
Date: 2026-06-08
---
**1. Profile Summary**
- Risk Score: 70 (High Risk)
- Ownership: Assigned to Bharti Airtel Ltd. (ASN 9498, IRT-BHARTI-IN)
- Geolocation: Bengaluru, Karnataka, India (12.98°N, 77.59°E)
- Network Role: Mobile carrier (LTE/5G)
- Threat Indicators: No direct malicious activity detected.
- DNSBL Listings: Listed on 4/8 DNSBLs (potential spam or abuse risk).
---
**2. Observation History**
- Recent Activity (June 8, 2026): Minimal risk signals (confidence: 30%).
- Long-Term Stability: No persistent malicious behavior (threat persistence: 0 days).
- Ownership Stability: Stable for >30 days.
- Geolocation Consistency: Plausible (India, Bengaluru).
---
**3. Relationships**
- Network Affiliation: Part of BHARTI-IN (182.79.0.0/18) subnet.
- Linked Entities: No direct connections to known malicious organizations or domains.
---
**4. Subnet Analysis**
- Subnet: 182.79.51.82/24
- Neighbor Risk: 1 high-risk neighbor (182.79.51.142, risk score: 80).
- Abuse Density: High (1/1 neighbors flagged).
- Total Siblings: 254 IPs in subnet; 1 actively flagged.
---
**5. Recommendations**
- Monitor Subnet: Focus on 182.79.51.142 due to higher risk.
- DNSBL Verification: Investigate DNSBL listings for spam or abuse patterns.
- Geolocation Validation: Confirm if the IPโs location aligns with Bharti Airtelโs infrastructure.
- Network Segmentation: Consider isolating high-risk subnets to mitigate potential lateral movement.
Conclusion: While the IP itself shows no direct threats, its subnet contains a high-risk neighbor. SOC teams should prioritize monitoring the subnet and validating DNSBL associations.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | IRT-BHARTI-IN |
| ASN | AS9498 |
| Network Name | BHARTI-IN |
| CIDR Block | 182.79.0.0/18 |
| RIR | APNIC |
| Country | IN |
| 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 | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
โ๏ธ Network Classification
| Infrastructure | Mobile |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown โ Insufficient routing data to classify |
๐ Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Server | โ |
| HTTP Title | โ |
๐ TLS Certificate
No certificate
Issued by โ
N/A
| SANs | None |
| Valid From | โ |
| Valid Until | โ |
๐ฏ Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 30% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 14% | 6 | 7 |
Coverage: 5/6 dimensions ยท Data sufficiency: partial
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-17 03:07:59 UTC |
| Last Seen | 2026-06-08 03:58:00 UTC |
| Profile Built | 2026-06-08 04:09:17 UTC |
| Data Freshness | Live |
| Signal Types | 15 |
| Total Observations | 15 |
๐ 15 signal types ยท 15 observations collected
This report is generated from 15+ 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.
Full dossier details are available via our API.
โน๏ธ 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.