IPDebrief

176.103.3.240

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.

IP Intelligence Briefing: 176.103.3.240

Date: 2026-06-13

---

**1. Core Profile**

- City: Balakliya, Kharkivs’ka Oblast’

- Coordinates: 49.46°N, 36.87°E

- Timezone: Europe/Kyiv

---

**2. Historical Observations**

---

**3. Network Relationships**

- High-Risk IPs: 176.103.3.3 (80), 176.103.3.139 (55), 176.103.3.203 (55).

- Low-Risk IPs: 176.103.3.19 (0), 176.103.3.224 (40).

---

**4. Threat Context**

---

**5. Recommendations**

1. Monitor Subnet: Track high-risk neighbors (e.g., 176.103.3.3, 176.103.3.139) for potential lateral movement.

2. Verify Geolocation: Investigate geo-plausibility discrepancy (false flag).

3. Network Segmentation: Ensure firewalled subnets are isolated from critical assets.

4. Threat Intelligence Feeds: Cross-check with DNSBLs (3 listings) and threat intelligence platforms.

---

Source: IPDebrief Threat Intelligence Platform.

Note: No immediate action required, but ongoing monitoring is advised due to mixed subnet risk levels.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡¦ Ukraine
RegionKharkivs’ka Oblast’
CityBalakliya
TimezoneEurope/Kyiv
Latitude49.46
Longitude36.87

🏒 Ownership & Registration

OrganizationDIALOGKOM-MNT
ASNAS56812
Network NameDIALOG-NET
CIDR Block176.103.0.0/19
RIRRIPE
CountryUA
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
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
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
25%
11
routing
25%
11
services
25%
11
ownership
0%
00
reputation
0%
00
geolocation
0%
00
Overall12%33
Coverage: 3/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-06-06 01:23:46 UTC
Last Seen2026-06-13 09:04:02 UTC
Profile Built2026-06-13 09:31:43 UTC
Data FreshnessLive
Signal Types16
Total Observations16
πŸ” 16 signal types Β· 16 observations collected
This report is generated from 16+ 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.