IPDebrief

185.17.125.112

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

Threat Intelligence Briefing: IP Address 185.17.125.112/32

Overview

Key Findings

1. Subnet Analysis

- Part of 185.17.125.0/24, classified as "mixed" with abuse density 28.57%.

- 9 high-risk neighbors (70+ score) and 10 threat-associated IPs in the subnet.

- Notable high-risk neighbors include:

- 185.17.125.42 (80), 185.17.125.52 (80), 185.17.125.114 (80).

2. Historical Trends

- Observed 14 times since May 30, 2026.

- Stable ownership (no recent changes) but inconsistent signal confidence (0.30–0.95).

- Inferred as part of a Yandex-linked network, though no direct ties to known campaigns.

3. Relationships

- Linked to BiT (network name) and Andrij Senyk (organization).

- No connections to Tor, CDN, or cloud infrastructure.

4. Behavioral Context

- No DNS resolution, TLS certificates, or HTTP services detected.

- DNSSEC valid but no email authentication (SPF/DKIM) configured.

Actionable Insights

Conclusion

While no direct malicious activity is observed, the IP’s high risk score, mixed subnet abuse density, and association with potential Yandex infrastructure suggest a need for further investigation. SOC teams should prioritize monitoring this IP and its neighbors for signs of compromise or anomalous behavior.

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 PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Serverβ€”
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
19%
22
routing
13%
11
services
13%
11
ownership
27%
23
reputation
13%
12
geolocation
19%
22
Overall17%911
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-14 23:35:27 UTC
Last Seen2026-06-19 11:33:39 UTC
Profile Built2026-06-18 20:26:04 UTC
Data FreshnessLive
Signal Types15
Total Observations15
πŸ” 15 signal types Β· 15 observations collected
This report is generated from 15+ 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.