Threat Intelligence Briefing: IP 192.210.193.135/32
Summary:
The IP address 192.210.193.135/32 was analyzed using a range of intelligence tools to determine its profile, historical activity, relationships, and neighborhood characteristics. The following narrative provides a comprehensive overview based on observed data.
Profile Information:
- Geolocation: The IP is associated with [Country, City], as determined by geolocation databases. This information provides context for potential origin and regional activity patterns.
- ASN and Organization: The IP address is assigned to [ASN] and belongs to [Organization Name]. The organization is typically involved in [Industry Type] and has a reputation for [Reputation Rating].
Observation History:
- Previous Activity: Historical data indicates that this IP address has been involved in [Number] distinct incidents over the past [Time Frame]. These incidents include [Types of Activities], such as [Specific Observations like DDoS, phishing attempts, etc.].
- Malicious Indicators: The IP has been flagged by multiple threat intelligence platforms as [Malicious/Not Malicious] based on its involvement in [Specific Threat Types]. There is evidence of [Types of Malware/Attacks] associated with this IP in the past.
Relationships:
- Known Associations: The IP address has been observed in conjunction with [Number of Related IPs] other IPs that share similar malicious behaviors or are part of the same botnet/attack campaign. These related IPs are primarily located in [Region] and have been implicated in [Specific Campaign Types].
- Infrastructure Links: There are known connections to [Infrastructure Types, e.g., C2 servers, proxy networks], which have facilitated [Specific Malicious Activities] in previous incidents.
Neighborhood Data:
- IP Range Proximity: The IP resides within a broader IP range that has been historically associated with [Type of Activity], such as [Specific Threats]. Other IPs within this range have shown patterns of [Malicious/Non-Malicious] behavior.
- Regional Trends: The surrounding IP neighborhood has exhibited increased activity related to [Specific Threat Trends], suggesting a potential hotspot for [Type of Cyber Threats].
Actionable Intelligence:
- Monitoring: It is recommended to closely monitor traffic originating from or directed to this IP address due to its historical involvement in [Types of Threats]. Implementing advanced filtering and detection mechanisms can help mitigate potential risks.
- Blocking/Whitelisting: Based on the malicious indicators and relationships, consider blocking this IP at network entry points. However, ensure that legitimate business processes are not disrupted by validating against whitelisted IPs or services.
- Incident Response: Prepare incident response plans in the event of a detected attack originating from or targeting this IP. Coordination with threat intelligence feeds can provide timely updates on related activity.
This intelligence briefing provides SOC analysts with the necessary information to assess risks associated with IP 192.210.193.135/32 and take appropriate defensive measures.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | HostPapa |
| ASN | AS36352 |
| Network Name | β |
| CIDR Block | β |
| RIR | ARIN |
| Country | β |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | 192-210-193-135-host.colocrossing.com |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 192-210-193-135-host.colocrossing.com |
π DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| 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 | 8% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 30% | 2 | 3 |
| Overall | 22% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-07 23:04:03 UTC |
| Last Seen | 2026-06-23 02:40:38 UTC |
| Profile Built | 2026-06-23 02:50:16 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 22 |
Full dossier details are available via our API.