IPDebrief

176.103.2.130

IP Intelligence Dossier
Your IP: 216.73.216.142

176.103.2.130 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to Balakliya, Ukraine. As of August 29, 2026, IPDebrief rates it Low Risk (15/100); no anonymizing service was detected.

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

# IPDEBRIEF INTELLIGENCE BRIEFING

Target IP: 176.103.2.130/32

Report Date: 2026-07-23

Classification: MODERATE RISK

---

## EXECUTIVE SUMMARY

IP 176.103.2.130 presents a moderate risk profile (score: 65/100) with no active threat indicators. The address is associated with DIALOG-NET infrastructure in Ukraine and operates with minimal service exposure. While currently classified as clean, the IP is listed on 3 DNS blacklist entries and should be monitored due to elevated risk scoring.

---

## OWNERSHIP & INFRASTRUCTURE

AttributeValue
**ASN**56812
**Organization**DIALOGKOM-MNT (DIALOG-NET)
**CIDR Block**176.103.0.0/19
**RIR**RIPE
**Registration**Not available

Network Classification: The IP is assigned to a firewalled network with no open services detected. No TLS certificates, HTTP titles, or server banners were observed during probing.

---

## GEOLOCATION

AttributeValue
**Country**Ukraine (UA)
**Region**Kharkivs'ka Oblast'
**City**Balakliya
**Timezone**Europe/Kyiv
**Geo Confidence**Low (geoPlausible: false)

*Note: Geolocation data shows low confidence with 500km accuracy radius and only one geo-source consensus.*

---

## THREAT ASSESSMENT

Risk Profile

Blacklist Status

Network Behavior

---

## NEIGHBORHOOD ANALYSIS

Subnet: 176.103.2.130/24

Risk Distribution:

The subnet shows minimal inherited risk (score: 1). One high-risk neighbor was observed at 176.103.2.4 (risk: 40), and 176.103.2.23 showed elevated scoring (55).

---

## SIGNAL HISTORY (16 Observations)

Recent observations (July 23, 2026) show:

No significant temporal escalation in threat behavior observed.

---

## CONTROL PLANE DATA

MetricValue
**Origin ASN**56812
**BGP Prefix**176.103.0.0/20
**Route Stability**False
**Route Changes (30d)**0
**RPKI State**Not available
**IRR Consistency**Not available
**DNSSEC Valid**True
**DNSBL Total Lists**8

---

## RELATIONSHIP MAPPING

The IP is associated with DIALOG-NET network entity. No additional relationships to hostnames, organizations, or certificates were detected.

---

## SECURITY RECOMMENDATIONS

Immediate Actions

1. Increase logging verbosity for traffic from this IP address

2. Review recent activity to confirm benign patterns

3. Implement firewall rules based on risk profile

Recommended Firewall Rules

```bash

# iptables

iptables -A INPUT -s 176.103.2.130 -j DROP

# nftables

nft add rule inet filter input ip saddr 176.103.2.130 drop

# nginx

deny 176.103.2.130;

```

Platform-Specific Actions

---

## ANALYST NOTES

---

END OF BRIEFING

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—

🛡️ 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
22%
11
routing
22%
11
services
22%
11
ownership
50%
23
reputation
0%
00
geolocation
35%
22
Overall25%78
Coverage: 5/6 dimensions · Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-07-05 11:42:43 UTC
Last Seen2026-10-06 08:47:52 UTC
Profile Built2026-08-29 05:20:37 UTC
Data FreshnessLive
Signal Types19
Total Observations20
🔍 19 signal types · 20 observations collected
This report is generated from 19+ 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.2.130

Who owns the IP address 176.103.2.130?

176.103.2.130 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.2.130 located?

Geolocation data places 176.103.2.130 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.2.130 malicious or safe?

176.103.2.130 currently carries a low risk assessment, meaning no significant threat indicators 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.