IPDebrief

176.103.4.155

IP Intelligence Dossier
Your IP: 216.73.216.142

176.103.4.155 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to Balakliya, Ukraine. As of November 6, 2026, IPDebrief rates it High Risk (80/100); no anonymizing service was detected.

{ } JSON
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP INTELLIGENCE BRIEFING

Target: 176.103.4.155/32

Date: Current Intelligence Cycle

Classification: MODERATE RISK

---

## EXECUTIVE SUMMARY

IP 176.103.4.155 is assigned to ASN 56812 (DIALOGKOM-MNT) within the 176.103.0.0/19 block, registered under RIR RIPE. Geolocation indicates Balakliya, Kharkivs'ka Oblast', Ukraine. The IP presents a moderate risk profile (risk score: 45/100) with no active threat indicators. No open services or ports detected; the IP appears firewalled. Despite lack of direct malicious activity, the IP is listed on 3 of 8 DNSBLs, warranting defensive monitoring.

---

## RISK ASSESSMENT

MetricValue
**Risk Score**45/100 (Moderate)
**Abuse Confidence**Not assessed
**DNSBL Listings**3 of 8 total lists
**Subnet Abuse Density**0.056 (moderate)
**Threat Persistence**0 days
**Campaign Correlation**None detected

---

## NETWORK CLASSIFICATION

---

## THREAT INDICATORS

Direct Indicators: None

Environmental Signals:

---

## OBSERVATION HISTORY

16 historical observations recorded. Recent signals (2026-07-28) indicate:

Temporal Analysis: The IP has shown no signs of escalating threat behavior over the observation window.

---

## NEIGHBORHOOD ANALYSIS

Subnet: 176.103.4.0/24

Total Siblings: 72

Active Siblings: 33

Threat Siblings: 1

High-Risk Neighbors Identified:

Implication: The /24 subnet demonstrates mixed risk characteristics. Target IP (155) operates at moderate risk while adjacent addresses show elevated threat activity.

---

## RELATIONSHIPS

---

## RECOMMENDED ACTIONS

The following firewall and WAF rules are recommended based on risk profile:

PlatformAction
**iptables**`iptables -A INPUT -s 176.103.4.155 -j DROP`
**nftables**`nft add rule inet filter input ip saddr 176.103.4.155 drop`
**nginx**`deny 176.103.4.155;`
**pfSense**`176.103.4.155/32`
**Cloudflare WAF**Block IP with expression `ip.src eq 176.103.4.155`
**AWS WAF**Add address `176.103.4.155/32` with description "IPDebrief risk 45"

---

## ANALYST NOTES

While the target IP shows no direct malicious activity, the presence of 3 DNSBL listings and the mixed-risk environment of the /24 subnet warrant defensive posture. The subnet contains multiple high-risk neighbors that may be exploited for lateral movement. Consider blocking at the perimeter and monitoring for any service changes. The IP is not associated with known campaigns or persistent malicious behavior.

---

*Intel generated by IPDebrief intelligence platform. Rules should be validated against operational requirements before deployment.*

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 Score0% (None)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECNot signed
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—

🛡️ Public Network Snapshot

Origin ASNAS56812
Network Prefix176.103.0.0/20
Route mappingFound

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
21%
24
routing
8%
11
services
12%
22
ownership
17%
23
reputation
8%
12
geolocation
39%
23
Overall18%1015
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-07-17 17:12:16 UTC
Last Seen2026-11-07 06:47:45 UTC
Profile Built2026-11-06 23:45:46 UTC
Data FreshnessLive
Signal Types21
Total Observations23
🔍 21 signal types · 23 observations collected
This report is generated from 21+ 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 📧 Enterprise Access

❓ Frequently Asked Questions About 176.103.4.155

Who owns the IP address 176.103.4.155?

176.103.4.155 is registered to DIALOGKOM-MNT. The address falls within the 176.103.0.0/19 network block. Registration is held at RIPE.

Where is 176.103.4.155 located?

Geolocation data places 176.103.4.155 in Balakliya, Kharkivs’ka Oblast’, Ukraine. The local time zone is Europe/Kyiv. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 176.103.4.155 malicious or safe?

176.103.4.155 currently carries a high risk assessment, meaning indicators associated with malicious or abusive activity have been observed. This assessment is generated from continuously collected signals and can change over time.

🏘️ Related IP Addresses

Nearby addresses in 176.103.0.0/19

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.