103.176.160.146
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 103.176.160.146
Date: 2026-06-11
---
**1. Risk Profile**
- Risk Score: 80/100 (High Risk)
- Threat Indicators: No active malware, phishing, or exploit campaigns detected.
- Network Classification: Firewalled / No Services (no open ports or TLS services).
- Geolocation: Registered to India (IN) under ASN 141526 (NOC MANAGER).
---
**2. Ownership & Network**
- Registrar: APNIC (AS141526)
- Organization: NOC MANAGER
- Subnet: 103.176.160.0/23
- Abuse Contact: Available via RDAP.
---
**3. Threat & Behavior**
- DNSSEC Valid: Yes
- DNSBL Listings: 5/8 lists (moderate risk).
- BGP Analysis: Route stability unknown; no recent changes.
- Behavioral Flags: No honeypot hits, enumeration, or WAF violations.
---
**4. Observation History**
- Last 30 Days: No significant changes in geolocation, DNS, or threat signals.
- Consensus: Geolocation inferred with 52% confidence (India).
---
**5. Relationships & Neighborhood**
- Linked Entities: Same network (JBNSOLPL) only.
- Subnet Abuse Density: 0% (no malicious neighbors detected).
---
**6. Recommended Actions**
- Block IP: Implement firewall rules to block traffic from 103.176.160.146.
- Monitor: Track DNS and BGP anomalies due to high risk score.
- Verify Ownership: Confirm NOC MANAGER’s legitimacy via RDAP.
Firewall Rules (Example):
- `iptables -A INPUT -s 103.176.160.146 -j DROP`
- Cloudflare WAF: Block IP with description "IPDebrief risk 80".
---
Conclusion:
This IP exhibits high risk due to its registration and network profile but shows no active malicious behavior. Block the IP and monitor for anomalies.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | NOC MANAGER |
| ASN | AS141526 |
| Network Name | JBNSOLPL |
| CIDR Block | 103.176.160.0/23 |
| 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 | Unknown |
| 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 | 19% | 2 | 2 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 19% | 2 | 2 |
| Overall | 17% | 9 | 11 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Fresh
| First Seen | 2026-05-27 19:21:16 UTC |
| Last Seen | 2026-06-26 14:30:46 UTC |
| Profile Built | 2026-06-18 22:47:59 UTC |
| Data Freshness | Fresh |
| Signal Types | 16 |
| Total Observations | 16 |
🔍 16 signal types · 16 observations collected
This report is generated from 16+ 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.