IPDebrief

95.85.238.18

IP Intelligence Dossier
Your IP: 216.73.217.131
{ } JSON 🔧 Full Actions API
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

## IP Intelligence Briefing: 95.85.238.18/32

Date: 2026-07-29

Classification: Moderate Risk

Risk Score: 50/100

---

Executive Summary

IP address 95.85.238.18 is a Czech Republic-based host with a moderate risk profile (50/100). The IP is associated with RDP services and exhibits directory enumeration activity targeting WordPress plugin paths. While not currently classified as a known attacker or persistent threat source, the IP operates within a subnet with 33% abuse density and has one active threat sibling. Recommended action: Block traffic at perimeter firewalls.

---

Technical Profile

Ownership & Registration:

Geolocation:

Network Classification:

Services & Ports:

---

Threat Indicators

Current Threat Status:

Abuse Context:

---

Observations & Activity History

Recent Activity (19 observations):

Temporal Analysis:

---

Neighborhood Analysis

Subnet: 95.85.238.0/24

Abuse Density: 33.33%

Classification: Mostly Clean

Sibling IPs:

IP AddressRisk ScoreAuthority Score
95.85.238.63NullNull
95.85.238.2092550

Threat Context: 1 threat sibling identified within subnet, indicating potential coordinated activity or shared infrastructure abuse.

---

Relationships

Connected Entities: 5 relationships identified

---

Recommended Actions

Firewall Rules (Block Recommended):

PlatformRule
iptables`iptables -A INPUT -s 95.85.238.18 -j DROP`
nftables`nft add rule inet filter input ip saddr 95.85.238.18 drop`
nginx`deny 95.85.238.18;`
pfSense`95.85.238.18/32` (block rule)
Cloudflare WAFBlock expression: `ip.src eq 95.85.238.18`
AWS WAFAddress: `95.85.238.18/32`

---

Intelligence Notes

1. RDP Exposure: The open RDP port (3389) represents a potential lateral movement target if the IP is compromised or being used as an attack vector.

2. WordPress Targeting: Directory enumeration activity suggests automated probing for WordPress installations, consistent with vulnerability scanning or credential harvesting operations.

3. Subnet Context: The 95.85.238.0/24 subnet exhibits elevated abuse density (33.33%). Consider applying broader subnet-level controls if organizational policy permits.

4. Risk Trend: No historical persistence detected; threat activity appears episodic rather than sustained.

---

Analyst Assessment: This IP warrants blocking at perimeter defenses due to moderate risk scoring and active reconnaissance behavior. Monitor for related IPs in the 95.85.238.0/24 subnet.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

Country🇨🇿 Czechia
Region—
CityLondon
TimezoneEurope/Prague
Latitude49.82
Longitude15.47
🛡️ Platform Security History
EnumerationPath/resource enumeration1
Total events: 1
Observed on 2026-07-29

🏢 Ownership & Registration

OrganizationDGTLS-MNT
ASNAS209946
Network NameALTAWK-CZ
CIDR Block95.85.238.0/24
RIRRIPE
CountryCZ
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)

🔐 DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierUnknown — Insufficient routing data to classify
No specific classification

🔌 Services & Open Ports

PortServiceProtocolBanner
3389rdptcp—
Closed Ports22, 25, 80, 443, 8080, 8443 (1 open / 7 scanned)
Server—
HTTP Title—

🔐 TLS Certificate

🔒
No certificate
Issued by —
N/A
SANsNone
Valid From—
Valid Until—
TLS ProtocolTls13
Cipher SuiteTLS_AES_128_GCM_SHA256
Signature Algorithmsha256RSA
Validity Period60 days

🛡️ Public Network Snapshot

Origin ASNAS209946
Network Prefix95.85.238.0/24
Route mappingFound
HSTSNot detected
CSPNot detected
HTTP/2Enabled

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
21%
24
routing
8%
11
services
28%
24
ownership
31%
25
reputation
8%
12
geolocation
17%
23
Overall19%1019
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-07-15 04:06:44 UTC
Last Seen2026-09-02 17:32:04 UTC
Profile Built2026-09-02 17:37:27 UTC
Data FreshnessLive
Signal Types22
Total Observations30
🔍 22 signal types · 30 observations collected
This report is generated from 22+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API 🔧 Actions API 📧 Enterprise Access

❓ Frequently Asked Questions About 95.85.238.18

Who owns the IP address 95.85.238.18?

95.85.238.18 is registered to DGTLS-MNT. The address falls within the 95.85.238.0/24 network block. Registration is held at RIPE.

Where is 95.85.238.18 located?

Geolocation data places 95.85.238.18 in London. The local time zone is Europe/Prague. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 95.85.238.18 malicious or safe?

95.85.238.18 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.

What ports are open on 95.85.238.18?

Responsive ports observed on 95.85.238.18 include 3389. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.

🏘️ Related IP Addresses

Nearby addresses in 95.85.238.0/24

Browse related networks

ℹ️ About This Report

All data shown is publicly available network metadata — IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.