INTELLECTUAL PROPERTY THREAT INTELLIGENCE BRIEFING
Subject IP: 103.135.138.166/32
Classification: LOW RISK
Risk Score: 25/100
Report Generated: Based on IPDebrief Intelligence Platform
---
EXECUTIVE SUMMARY
The target IP address 103.135.138.166 presents as a low-risk endpoint with no active threat indicators. The IP is geolocated to Dhaka, Bangladesh and operates within the 103.135.138.0/24 subnet (AS150774). No malicious behavior, known campaigns, or threat feed matches were identified during analysis. The IP currently shows no open services and no associated threat indicators.
---
GEOLOCATION & NETWORK ATTRIBUTES
- Country: Bangladesh (BD)
- City: Dhaka
- Coordinates: 23.7°N, 90.37°E
- ASN: 150774
- BGP Prefix: 103.135.138.0/24
- Ownership Data: Unavailable (no org name, netname, or abuse contact registered)
- Network Role: Firewalled / No Services Detected
---
THREAT INTELLIGENCE
- Risk Assessment: Low Risk (Score: 25)
- Threat Indicators: None detected
- Known Attacker: No
- Tor Exit Node: No
- Spam Source: No
- Blacklist Status: Not listed (0 counts)
- Campaign Correlation: 0 matches
- Abuse Confidence Score: Not applicable
---
SERVICE & DNS ANALYSIS
- Open Ports: None detected
- DNS Resolution: Forward resolution not confirmed
- PTR Records: None
- Hosted Domains: 0
- Email Authentication: N/A (no hosted domain)
---
TEMPORAL ANALYSIS (OBSERVATION HISTORY)
Nine signals were observed over the monitoring period. Recent activity includes:
- Geolocation signals consistently identifying Bangladesh (Dhaka)
- ASN identification: AS59239 (itel limited)
- Subnet classification: Clean with 0 abuse density
- Operator score: 0.1304 (Minimal)
- No evidence of threat persistence or malicious activity escalation
---
NEIGHBORHOOD ANALYSIS
- Subnet: 103.135.138.166/24
- Abuse Density: 0
- Classification: Clean
- Total Siblings: 1
- Active Threat Siblings: 0
- High/Medium Risk Neighbors: 0
---
RELATIONSHIP GRAPH
No relationships were discovered in the relationship graph (no links to subnets, hostnames, organizations, or certificates).
---
RECOMMENDED ACTIONS
Based on the low-risk profile and absence of threat indicators:
- No immediate blocking recommended
- Standard monitoring practices apply
- No specific firewall rules generated (risk score below threshold)
---
INTELLIGENCE CONCLUSION
The IP address 103.135.138.166/32 should be treated as a benign endpoint. No malicious activity, known attack patterns, or threat intelligence associations were identified. The subnet demonstrates clean classification with zero abuse density. SOC teams may maintain standard monitoring protocols without escalation.
Data Confidence: Low (limited ownership data and relationship information available)
---
*Intelligence sourced from IPDebrief Platform. All data derived from automated reconnaissance and threat feed analysis.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IRT-SPIDERNET-BD |
| ASN | AS150774 |
| Network Name | SPIDERNET-BD |
| CIDR Block | 103.135.136.0/22 |
| RIR | APNIC |
| Country | BD |
| 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 | — |
🛡️ Public Network Snapshot
| Origin ASN | AS150774 |
| Network Prefix | 103.135.138.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 12% | 2 | 2 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 8% | 1 | 2 |
| geolocation | 8% | 1 | 1 |
| Overall | 11% | 9 | 11 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-08 06:53:43 UTC |
| Last Seen | 2026-08-27 02:15:54 UTC |
| Profile Built | 2026-08-29 06:30:20 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 19 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 103.135.138.166
Who owns the IP address 103.135.138.166?
103.135.138.166 is registered to IRT-SPIDERNET-BD. The address falls within the 103.135.136.0/22 network block. Registration is held at APNIC.
Where is 103.135.138.166 located?
Geolocation data places 103.135.138.166 in Boston, US-MA, United States. The local time zone is America/New_York. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 103.135.138.166 malicious or safe?
103.135.138.166 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.