IPDebrief

182.95.52.122

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: 182.95.52.122

Date: 2026-06-17

---

**1. Risk Profile**

- 6 DNSBL listings (high severity)

- Open SSH service (port 22)

- No known malware campaigns or spam sources

---

**2. Geolocation & Ownership**

---

**3. Network Behavior**

- Open SSH (SSH-2.0-OpenSSH_8.9)

- No TLS/HTTP services detected

- No PTR records or domain associations

- DNSSEC validated

- BGP prefix: 182.95.52.0/24

- DNSBL listings (6/8 total)

- Route stability: Unstable (0 route changes in 30 days)

---

**4. Observation History**

- 6 DNSBL listings (high severity)

- No changes in ownership or threat indicators

- Persistent mobile network association

---

**5. Relationships**

- Same network: BHARTI-IN (AS 9498)

- No direct ties to known malicious organizations or campaigns

---

**6. Neighborhood Analysis**

- 182.95.52.170 (Risk Score: 80)

---

**7. Recommendations**

1. Block SSH Access: Restrict or monitor SSH connections to this IP due to open port 22.

2. Monitor DNSBL Listings: Investigate the 6 DNSBL associations (e.g., Spamhaus, Barracuda).

3. Isolate Mobile Traffic: Consider filtering traffic from Bharti Airtelโ€™s LTE/5G network.

4. Watch Neighbors: 182.95.52.170 shares the same subnet and high-risk profile.

5. Verify DNSSEC: Confirm DNSSEC validation for mitigating spoofing risks.

---

Source: IPDebrief Threat Intelligence Platform

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฎ๐Ÿ‡ณ India
RegionNew
CityPhase III
Timezoneโ€”
Latitude22.00
Longitude79.00

๐Ÿข Ownership & Registration

OrganizationIRT-BHARTI-IN
ASNAS9498
Network NameBHARTI-IN
CIDR Block182.95.0.0/17
RIRAPNIC
CountryIN
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 Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureMobile
Service PurposeSingle-Service Host
Network TierUnknown โ€” Insufficient routing data to classify
Mobile

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
22sshtcp
Closed Ports25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned)
Serverโ€”
HTTP Titleโ€”
SSH VersionSSH-2.0-OpenSSH_9.8

๐Ÿ” 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
30%
23
routing
13%
11
services
15%
22
ownership
27%
23
reputation
15%
12
geolocation
32%
23
Overall22%1014
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:03:59 UTC
Last Seen2026-06-23 00:01:31 UTC
Profile Built2026-06-23 00:07:38 UTC
Data FreshnessLive
Signal Types18
Total Observations19
๐Ÿ” 18 signal types ยท 19 observations collected
This report is generated from 18+ 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.