103.38.68.3
IP Intelligence Briefing: 103.38.68.3
Date: 2026-06-02
**Risk Assessment**
- Overall Risk: Low (Risk Score: 25)
- Threat Indicators: No active malware, phishing, or exploit campaigns detected.
- Network Stability: Firewalled infrastructure with no open services (ports, TLS, or HTTP).
**Ownership & Geolocation**
- ISP: IRT-IN-IMCL (ASN 17665, APNIC registry).
- Location: Mumbai, Maharashtra, India (geolocation inferred with 52% confidence).
- Subnet: 103.38.68.0/24 (abuse density: 1/1000, classified as "mostly clean").
**Threat Observations**
- Scans: Detected TLS/SSL scan attempts (low confidence) and DNS enumeration (high severity).
- Behavioral: No honeypot hits, enumeration strikes, or WAF violations.
- Historical Trends: No persistent malicious activity; threat observation count: 1.
**Network Relationships**
- ISP Connections: Linked to "Onebroadband" (same network).
- Subnet Context: No active malicious neighbors; 0/1000 IPs in subnet flagged for abuse.
**Actionable Insights**
1. Monitor Subnet: While the subnet is currently clean, the low abuse density may mask covert operations.
2. Verify Geolocation: Cross-check IP with Mumbai ISP records due to inferred location.
3. Inspect DNS: Investigate DNS listings for potential misconfigurations or hidden services.
4. Maintain Firewalls: Current firewall rules align with low-risk posture; no immediate blocking required.
Conclusion: 103.38.68.3 exhibits no direct malicious activity but warrants continued monitoring for anomalies in its subnet or network behavior.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IRT-IN-IMCL |
| ASN | AS17665 |
| 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 | 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 | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| 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 | 31% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 22% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:27 UTC |
| Last Seen | 2026-06-22 07:14:02 UTC |
| Profile Built | 2026-06-22 07:14:57 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 20 |
Full dossier details are available via our API.