IPDebrief

185.17.125.63

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

Threat Intelligence Briefing: IP 185.17.125.63/32

Observation Summary:

The IP address 185.17.125.63/32, associated with a web server located in Russia, was observed conducting activities that may be of interest to security operations center (SOC) analysts. The analysis is based on data gathered through various threat intelligence tools, focusing on its profile, historical observations, relationships, and neighborhood data.

Profile:

Observation History:

Relationships:

Neighborhood Data:

Actionable Intelligence:

SOC analysts should consider the following actions based on the observed data:

1. Monitoring and Blocking: Implement monitoring for traffic originating from or directed to this IP, and consider blocking it to prevent potential security breaches.

2. Incident Response Preparation: Prepare incident response plans for possible phishing or DDoS scenarios involving this IP.

3. Threat Intelligence Sharing: Share findings with relevant threat intelligence communities to enhance collective understanding and mitigation strategies.

4. Vulnerability Management: Ensure systems are patched against known vulnerabilities that could be exploited by malicious content served from this IP.

This intelligence briefing provides a concise overview of the activities associated with IP 185.17.125.63/32, enabling SOC teams to make informed decisions in protecting their networks.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡¦ Ukraine
RegionLviv
City79070
TimezoneEurope/Kyiv
Latitude50.45
Longitude30.53

🏒 Ownership & Registration

OrganizationAndrij Senyk
ASNAS3255
Network Nameβ€”
CIDR Blockβ€”
RIRRIPE
Countryβ€”
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
80httptcpβ€”
443httpstcpβ€”
Closed Ports22, 25, 3389, 8080, 8443 (2 open / 7 scanned)
Serverlighttpd/1.4.39
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
27%
24
routing
13%
11
services
30%
24
ownership
24%
23
reputation
22%
13
geolocation
19%
22
Overall22%1017
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-12 09:40:42 UTC
Last Seen2026-06-26 18:10:54 UTC
Profile Built2026-06-26 16:36:20 UTC
Data FreshnessLive
Signal Types18
Total Observations19
πŸ” 18 signal types Β· 19 observations collected
This report is generated from 18+ 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

ℹ️ 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.