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.95.103.74
*Generated via IPDebrief Analysis*
---
**1. Core Profile**
- Risk Score: 80 (High Risk)
- Ownership: Registered to IRT-BHARTI-IN (Bharti Airtel Ltd., India) under ASN 9498.
- Geolocation: New Delhi, India (Phase III, New).
- Network Role: Mobile device (LTE/5G) on Bharti Airtel network.
- Threat Indicators: No direct malicious activity detected. DNSSEC is valid, but 6 DNSBL lists flag the IP.
- Services: No open ports or TLS certificates identified.
---
**2. Observation History**
- Recent Activity:
- Detected in 2026 with mixed confidence signals (0.21โ0.95).
- One observation linked to AlienVault OTX (13 pulse alerts, including potential threats).
- Subnet abuse density: 1/10 (mostly clean, but 4/4 neighboring IPs flagged as high risk).
- Trend: No persistent malicious activity; threat observation count is low.
---
**3. Network Relationships**
- Shared Network: Part of BHARTI-IN (Bharti Airtel) network.
- Neighbors:
- 182.95.103.110, 182.95.103.150, 182.95.103.198 (all high-risk, 80/100 score).
- Subnet: 182.95.103.0/24 (abuse density: 1/10).
---
**4. Recommendations**
- Monitor Closely: Despite no direct threats, the IPโs mobile carrier context and high-risk neighbors warrant scrutiny.
- Check for Compromises: Investigate if the device is part of a compromised mobile network or botnet.
- Block Neighbors: Consider mitigating the high-risk subnet (182.95.103.0/24) due to elevated abuse density.
- Verify DNSSEC: Ensure DNSSEC validation is enforced for this subnet to prevent spoofing.
Note: No immediate action required for this IP, but contextualize within the broader network risk.
---
*End of Briefing*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | IRT-BHARTI-IN |
| ASN | AS9498 |
| Network Name | โ |
| CIDR Block | โ |
| RIR | APNIC |
| 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 | 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 | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| 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 | 32% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 18% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 22% | 10 | 15 |
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-07 23:03:59 UTC |
| Last Seen | 2026-06-26 18:10:52 UTC |
| Profile Built | 2026-06-22 23:49:08 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 19 |
๐ 17 signal types ยท 19 observations collected
This report is generated from 17+ 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.