IPDebrief

178.217.169.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: 178.217.169.240

Date: 2026-06-02

---

**Risk Profile**

---

**Ownership & Geolocation**

---

**Threat Observations**

- Detected scanning attempts (ports scanned), but no open services found.

- Traceroute failed due to ICMP blocking, limiting geographic validation.

- No DNSBL listings, no TLS certificate mismatches, no known attacker campaigns.

- Low pulse count (20) from open-source threat feeds, but no confirmed threats.

---

**Network Relationships**

- Subnet: 178.217.169.0/24 (abuse density: 0%, classified as "clean").

- BGP Prefix: 178.217.168.0/21 (KRENA-MNT).

- No peer IPs or subdomains linked.

---

**Behavioral Analysis**

- No HTTP/HTTPS activity, no email authentication records (SPF/DKIM).

- No TLS certificates or server banners detected.

- Route stability flagged as "unstable" (BGP route changes).

- ICMP blocking suggests network filtering or security measures.

---

**Recommendations**

1. Monitor Subnet: Track 178.217.169.0/24 for unusual traffic patterns, as the IPโ€™s network role is unclear.

2. Validate Geolocation: Confirm Kyrgyzstan origin via alternative methods (e.g., IP geolocation tools).

3. Check for Configuration Changes: Ensure firewalled services are properly configured to block unauthorized access.

4. Maintain Baseline: No immediate action required, but continue monitoring for anomalies.

---

Source: IPDebrief Threat Intelligence Platform

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฐ๐Ÿ‡ฌ KG
Regionโ€”
Cityโ€”
Timezoneโ€”
Latitude41.00
Longitude75.00

๐Ÿข Ownership & Registration

OrganizationKRENA-MNT
ASNAS197119
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
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
35%
23
routing
13%
11
services
15%
22
ownership
24%
23
reputation
17%
12
geolocation
19%
22
Overall20%1013
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-07 23:03:57 UTC
Last Seen2026-06-22 22:42:28 UTC
Profile Built2026-06-22 22:52:37 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.