IP Intelligence Briefing: 194.44.140.128
Date: 2026-06-09
---
**1. Risk Profile**
- Risk Score: 80 (High Risk)
- Provider/Authority Scores: 0/0 (No identifiable ISP or authority)
- Threat Indicators: No direct malicious activity detected (no known campaigns, spam, or attacker associations).
- DNSBL Listings: 5/8 DNSBL lists flagged the IP (moderate abuse risk).
---
**2. Ownership & Geolocation**
- AS: AS3255 (UARNET-RADIOSERVICE-WIFI-20050629)
- Country: Ukraine (Lviv)
- Subnet: 194.44.140.0/24
- Registration: Registered to "UARNET-RADIOSERVICE-WIFI-20050629" (RIPE)
- Abuse Contact: Available via RDAP (abuse@radioservice.net.ua)
---
**3. Network Behavior**
- Services: No open ports, TLS certs, or HTTP services detected.
- Routing: BGP prefix 194.44.140.0/24 shows unstable routes (route changes in last 30 days).
- DNSSEC: Validated (no DNSSEC issues).
- Subnet Abuse Density: 11.5% (11 high-risk neighbors in 96 total).
---
**4. Observation History**
- Recent Activity (Last 30 Days):
- Minimal risk score (0.13) as of 2026-06-09.
- No persistent malicious activity or threat persistence.
- DNSBL listings remained consistent (5/8 lists).
- Historical Trends: No significant changes in geolocation or ownership.
---
**5. Relationships**
- Network Links:
- Directly tied to the UARNET-RADIOSERVICE-WIFI-20050629 network (same subnet).
- No connections to known malicious organizations or subnets.
---
**6. Neighborhood Analysis**
- Subnet (194.44.140.0/24):
- 96 total IPs, with 11 high-risk (risk score β₯70), 57 medium-risk (50β69), and 28 low-risk.
- Top Risky Neighbors:
- 194.44.140.5 (55), 194.44.140.8 (70), 194.44.140.11 (55).
- Abuse Density: 11.5% (moderate risk).
---
**7. Recommendations**
- Monitor Subnet: The 194.44.140.0/24 subnet has a moderate abuse density. Investigate high-risk neighbors (e.g., 194.44.140.5, 194.44.140.8).
- Check DNSBL Status: Verify if the IP is listed on 5/8 DNSBLs and consider blocking or rate-limiting.
- Network Segmentation: Isolate this IP or subnet if it connects to internal systems, given the lack of service activity and DNSBL flags.
- Validate Ownership: Confirm the legitimacy of the "UARNET-RADIOSERVICE-WIFI-20050629" network via RIPE or direct contact.
---
Note: No active threats or services detected, but the IPβs DNSBL listings and subnet abuse density warrant further investigation.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | AS3255-MNT |
| ASN | AS3255 |
| Network Name | UARNET-RADIOSERVICE-WIFI-20050629 |
| CIDR Block | 194.44.140.0/24 |
| RIR | RIPE |
| Country | UA |
| 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 | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 30% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 14% | 6 | 7 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-21 20:59:52 UTC |
| Last Seen | 2026-06-09 14:36:06 UTC |
| Profile Built | 2026-06-09 14:45:10 UTC |
| Data Freshness | Live |
| Signal Types | 14 |
| Total Observations | 14 |
Full dossier details are available via our API.