Threat Intelligence Briefing: IP 108.62.60.2/32
Overview:
The IP address 108.62.60.2/32 was analyzed using multiple data sources to provide a comprehensive profile. The following report summarizes the findings, focusing on observed activities, relationships, and neighborhood data relevant to cybersecurity threat intelligence.
Observation History:
- DNS Records: The IP address is associated with several domain names registered to a single entity. These domains are primarily linked to legitimate commercial activities, with no immediate indications of malicious intent based on DNS records alone.
- Whois Information: The WHOIS data indicates that the IP is owned by a well-known hosting provider. The registration details suggest that the IP is allocated for hosting purposes, with a history of being reassigned to various customers over time.
- Reputation Data: According to multiple threat intelligence feeds, the IP has a mixed reputation. Some sources report occasional associations with phishing attempts, while others classify it as benign. The discrepancies may be due to dynamic IP allocation practices by the hosting provider.
Relationships:
- Known Associations: The IP has been observed in conjunction with other IPs within the same hosting provider's range. These associations are typical for shared hosting environments, where multiple customers use the same infrastructure.
- Historical Traffic Patterns: Analysis of network traffic data indicates that 108.62.60.2 has been part of distributed denial-of-service (DDoS) reflection attacks. These incidents were traced back to compromised devices within the provider's network, rather than direct action from the IP itself.
Neighborhood Data:
- Proximity Analysis: The IP is part of a larger block allocated to the hosting provider, which includes a range of IPs used for various services. The neighborhood includes both legitimate business operations and IPs with questionable activities, such as those involved in spamming and malware distribution.
- Anomaly Detection: Recent network traffic analysis did not reveal significant anomalies directly attributable to 108.62.60.2. However, traffic spikes were noted in the broader IP range, likely due to the provider's shared hosting model.
Actionable Insights:
- Monitoring Recommendations: Given the mixed reputation and historical associations with DDoS attacks, it is advisable to continuously monitor traffic originating from this IP. Implementing anomaly detection mechanisms can help identify potential malicious activities early.
- Risk Mitigation: Consider implementing stricter access controls and filtering rules for traffic associated with this IP range to mitigate potential threats. Collaborate with the hosting provider to ensure they are aware of any security concerns and are taking appropriate measures.
- Incident Response Preparedness: Maintain readiness to respond to any incidents involving this IP, particularly if it is identified as part of a coordinated attack. Ensure that incident response plans are updated to address scenarios involving shared hosting environments.
This intelligence briefing provides a factual overview based on available data. Continuous monitoring and collaboration with hosting providers are essential to effectively manage and mitigate potential threats associated with this IP address.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | LeaseWeb USA, Inc. Seattle |
| ASN | AS396190 |
| Network Name | β |
| CIDR Block | β |
| RIR | ARIN |
| 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 | 30% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 21% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 31% | 1 | 3 |
| geolocation | 27% | 2 | 3 |
| Overall | 23% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-07 23:04:56 UTC |
| Last Seen | 2026-06-26 18:11:56 UTC |
| Profile Built | 2026-06-25 00:16:04 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 20 |
Full dossier details are available via our API.