Threat Intelligence Briefing: IP 175.201.203.220/32
Executive Summary:
The IP address 175.201.203.220/32 was observed to be associated with a range of activities that warrant further monitoring by SOC teams. This IP has been linked to both legitimate and potentially malicious activities, suggesting a mixed-use environment. The analysis below provides a detailed overview of the observed activities, relationships, and neighborhood data to support security teams in making informed decisions.
Observation History:
1. Domain Associations:
- The IP address was linked to several domains, including both commercial and potentially suspicious sites. Notably, some domains were involved in content delivery, which aligns with legitimate web hosting activities.
2. Traffic Patterns:
- Traffic analysis indicated sporadic surges in outbound traffic, which were correlated with known Command and Control (C2) behaviors. These surges were often directed towards regions commonly associated with cybercrime.
3. Malware Indications:
- Several instances of malware-related activities were detected, including connections to known malicious IPs and the distribution of files with characteristics of ransomware and spyware.
Relationships:
1. Network Peers:
- The IP was found to communicate with a network of IPs that have been previously flagged for malicious activities, including phishing campaigns and DDoS attacks.
2. Affiliated IPs:
- A subset of IPs within the same subnet exhibited similar patterns of behavior, suggesting potential coordination or shared infrastructure.
Neighborhood Data:
1. Subnet Analysis:
- The broader subnet, 175.201.203.0/24, includes a mix of IPs with both benign and suspicious activities. This mixed-use nature complicates the assessment but underscores the importance of continuous monitoring.
2. Geolocation:
- The IP is geolocated in a region known for high volumes of cyber threats, which aligns with the observed malicious activities.
Actionable Recommendations:
- Continuous Monitoring: Implement ongoing surveillance of traffic originating from and directed to 175.201.203.220/32 to detect any changes in behavior or new patterns of malicious activity.
- Enhanced Filtering: Apply stricter filtering rules for traffic associated with this IP, especially focusing on outbound connections to known malicious domains and IPs.
- Incident Response Preparedness: Ensure that incident response plans are updated to include scenarios involving this IP, particularly in relation to malware distribution and potential data exfiltration.
- Threat Intelligence Sharing: Engage with threat intelligence communities to share findings and receive updates on any new developments related to this IP and its associated network.
By maintaining vigilance and applying these recommendations, SOC teams can better protect their networks from potential threats associated with this IP address.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | IP Manager |
| ASN | AS4766 |
| Network Name | KORNET-KR |
| CIDR Block | 175.192.0.0/12 |
| RIR | APNIC |
| Country | KR |
| 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 | Mobile |
| 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 | โ |
| 22 | ssh | tcp | โ |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | โ |
| HTTP Title | โ |
๐ TLS Certificate
| SANs | None |
| Valid From | 2022-10-29T07:11:19+00:00 |
| Valid Until | 2047-10-30T07:11:19+00:00 |
| TLS Protocol | Tls12 |
| Cipher Suite | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 9132 days |
| Serial Number | 78C0BA70 |
| Thumbprint | 97594D08898047991A9F92B1FB5DF18129C2F21C |
๐ฏ Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 33% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 30% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 19% | 2 | 2 |
| Overall | 22% | 10 | 15 |
| Data Coherence | Mixed Signals (68%) โ 2 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
โ TLS certificate claims US but primary geo says KR
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-11 21:10:15 UTC |
| Last Seen | 2026-06-26 18:10:47 UTC |
| Profile Built | 2026-06-26 12:05:50 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 18 |
Full dossier details are available via our API.