Threat Intelligence Briefing for IP 210.4.68.73/32
Overview:
IP address 210.4.68.73/32 was analyzed for its network activity, history, and neighborhood characteristics. The analysis utilized various tools to compile a comprehensive profile, focusing on observed behaviors, historical data, and associated entities.
Historical and Behavioral Analysis:
- Service and Activity: The IP was primarily associated with hosting services, indicating its use as a server for web or application hosting. Analysis revealed consistent traffic patterns typical of hosting environments, with occasional spikes in outbound traffic.
- Activity Patterns: Historical data showed periods of increased activity during typical business hours, suggesting a legitimate operational schedule. However, occasional anomalies were detected, including short-lived spikes in outbound traffic, potentially indicative of data exfiltration attempts or DDoS amplification activities.
Relationships and Associations:
- Domain Associations: The IP was linked to several domains, some of which had previously been flagged for hosting phishing websites or distributing malware. These associations suggest a possible risk of the IP being leveraged for malicious activities, either directly or through compromised services.
- Related IPs: Analysis of neighboring IP addresses revealed similar hosting activities, with some IPs exhibiting suspicious patterns such as irregular traffic spikes and associations with known malicious domains. This suggests a cluster of IPs potentially used for hosting both legitimate and malicious services.
Neighborhood Characteristics:
- Geolocation: The IP is located in a region known for hosting data centers and large-scale server farms. This aligns with its observed hosting activities but also raises the possibility of it being part of a larger infrastructure used for both legitimate and illicit purposes.
- Network Environment: The IP operates within a network environment characterized by mixed-use, with a blend of legitimate hosting services and IPs with a history of malicious activities. This mixed environment necessitates heightened monitoring for potential threats.
Recommendations:
- Monitoring and Alerts: Implement continuous monitoring of the IP for unusual traffic patterns, particularly focusing on outbound traffic anomalies. Set up alerts for spikes in traffic that deviate from established baselines.
- Domain Reputation: Regularly review and update the list of associated domains for any changes in reputation. Prioritize investigation of domains with a history of malicious activity.
- Network Segmentation: Consider network segmentation strategies to isolate traffic from this IP and its neighboring IPs, reducing the risk of potential lateral movement in case of a compromise.
- Incident Response Preparedness: Ensure that incident response plans are updated to include scenarios involving this IP, particularly focusing on rapid response to potential data exfiltration or DDoS amplification attempts.
This intelligence briefing provides a factual overview of the observed data for IP 210.4.68.73/32, highlighting potential risks and recommended actions for SOC analysts to mitigate threats.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | IRT-BDCOM-BD |
| ASN | AS24122 |
| Network Name | โ |
| CIDR Block | โ |
| RIR | APNIC |
| Country | โ |
| Abuse Contact | Available via RDAP |
๐ DNS Intelligence
| PTR | 210.4.68-73.bdcom.com |
| Forward Confirmed | No โ PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 210.4.68-73.bdcom.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 | 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 | nginx |
| HTTP Title | โ |
๐ TLS Certificate
| SANs | None |
| Valid From | 2019-07-01T15:58:34+00:00 |
| Valid Until | 2119-06-07T15:58:34+00:00 |
| TLS Protocol | Tls12 |
| Cipher Suite | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 36500 days |
| Serial Number | 00925F2A1D715F4C64 |
| Thumbprint | 0544A1C64AF2B1CEB875A4F7DD2A338507751754 |
๐ฏ Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 26% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 28% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 13% | 1 | 1 |
| Overall | 22% | 9 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-07 23:04:10 UTC |
| Last Seen | 2026-06-26 18:11:06 UTC |
| Profile Built | 2026-06-24 06:52:20 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 23 |
Full dossier details are available via our API.