193.8.186.37
IP Intelligence Briefing: 193.8.186.37/32
Date: 2026-06-06
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Ownership: Assigned to "Abuse-C Role" (ASN 201002, RIPE).
- Geolocation:
- Country: GB (United Kingdom)
- City: Singapore (discrepancy noted; may indicate misconfigured DNS or spoofing).
- Network Role: Firewalled / No Services (no open ports, TLS, or HTTP detected).
- Threat Indicators: No malicious activity, spam, or known attacker associations.
---
**2. Observation History**
- Latest Activity:
- 2026-06-06: Low-confidence DNS listing (0.50) and geolocation data (Singapore).
- 2026-05-29: ASN allocation records (RIPE) and subnet abuse density analysis (0.3333).
- Trends: No persistent malicious behavior; IP has not been flagged in threat feeds or blacklists.
---
**3. Relationships**
- Linked Entities:
- Subnet: 193.8.186.0/24 (classified as "mostly_clean").
- Organization: CojuhariSolutions (Abuse-C Role, RIPE).
- Connections: No direct links to known malicious domains, hosts, or certificates.
---
**4. Neighborhood Analysis**
- Subnet: 193.8.186.37/24
- Neighbor IPs:
- 193.8.186.33: Risk Score 25 (Low).
- 193.8.186.35: Risk Score 25 (Low).
- Abuse Density: 0% (no high-risk siblings).
---
**5. Actionable Insights**
- No Immediate Threat: The IP shows no signs of malicious activity, spam, or network exploitation.
- Monitor Geolocation Discrepancy: Investigate the conflicting geolocation data (GB vs. Singapore) for potential spoofing or misconfiguration.
- Watch Subnet Activity: While the subnet is mostly clean, continue monitoring for abnormal traffic patterns or new risk indicators.
Recommendation: No urgent action required. Maintain standard monitoring protocols and verify geolocation inconsistencies.
---
*Generated by IPDebrief Intelligence Platform*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Abuse-C Role |
| ASN | AS201002 |
| Network Name | — |
| CIDR Block | — |
| RIR | RIPE |
| 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 | |||
| 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 | 27% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 24% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 19% | 2 | 2 |
| Overall | 19% | 9 | 13 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-11 08:58:18 UTC |
| Last Seen | 2026-06-26 08:34:56 UTC |
| Profile Built | 2026-06-26 08:43:38 UTC |
| Data Freshness | Live |
| Signal Types | 15 |
| Total Observations | 16 |
Full dossier details are available via our API.