103.57.176.18
IP Intelligence Briefing: 103.57.176.18
Date: 2026-06-08
---
**1. Profile Summary**
- Risk Score: Moderate (55/100)
- Ownership: Registered to *SanjeevKumar Tyagi* (ASN 59162, APNIC).
- Geolocation: India (IN), with coordinates 22°N, 79°E.
- Network Role: Firewalled / No Services detected.
- Threat Indicators: No active malicious indicators (no malware, phishing, or C2 activity).
---
**2. Observation History**
- Latest Activity: June 7, 2026 (confidence: 85%).
- Threat Listings:
- Listed in 4/8 threat feeds (high-severity categories).
- DNSSEC and CAA records validated, but DNS resolution errors observed.
- Network Stability: Route instability detected (fluctuating BGP prefixes).
---
**3. Relationships**
- Network Affiliation: Linked to the *MISPL* network (ASN 59162).
- DNS Associations:
- Failed DNS queries to 192.168.2.108 (likely internal or misconfigured resolver).
- Certificates: No TLS/SSL certificates or HTTP services detected.
---
**4. Neighborhood Analysis**
- Subnet: 103.57.176.0/24.
- Neighbor Risk:
- 103.57.176.19: High risk (80/100).
- 103.57.176.202: Medium risk (70/100).
- Abuse Density: 50% of subnet IPs show risk indicators.
---
**5. Risk Assessment & Recommendations**
- Immediate Actions:
- Monitor neighbors (103.57.176.19/202) for suspicious activity.
- Investigate DNS resolution failures (192.168.2.108).
- Verify network segmentation to isolate high-risk subnets.
- Long-Term Mitigation:
- Validate ownership of 103.57.176.18/24 with APNIC.
- Implement DNS monitoring to detect misconfigurations.
---
Note: No direct malicious activity detected, but elevated risks in the subnet warrant further scrutiny.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IRT-MISPL-IN |
| ASN | AS59162 |
| Network Name | MISPL |
| CIDR Block | 103.57.176.0/22 |
| 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 | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Present |
☁️ Network Classification
| Infrastructure | Unknown |
| 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 | lighttpd/1.4.39 |
| HTTP Title | — |
🔐 TLS Certificate
| 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 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 13% | 1 | 1 |
| Overall | 16% | 8 | 11 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-15 14:44:33 UTC |
| Last Seen | 2026-06-20 11:58:00 UTC |
| Profile Built | 2026-06-07 13:34:45 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 22 |
Full dossier details are available via our API.