IPDebrief

43.225.68.34

IP Intelligence Dossier
Your IP: 216.73.216.5
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP Intelligence Briefing: 43.225.68.34/32

## Executive Summary

IP 43.225.68.34 presents a moderate-risk threat profile (55/100) with elevated DNSBL listings and conflicting geolocation data. The IP is classified as "clean" at the /24 subnet level but requires enhanced monitoring due to blacklist associations and risk indicators.

## Risk Assessment

## Technical Profile

## Threat Indicators

## Historical Observations (11 observations)

Recent activity shows conflicting signals:

## Subnet Neighborhood Analysis

## Recommended Actions

SOC Analyst Priority: MEDIUM

1. Logging: Increase logging verbosity for traffic from this IP address

2. Firewall Blocking: Consider blocking at perimeter based on risk score 55/100

3. Monitoring: Track for any changes in behavior or service exposure

Recommended Firewall Rules:

## Intelligence Conclusion

While the /24 subnet shows no abuse activity, the target IP warrants monitoring due to DNSBL associations and unstable routing behavior. The IP shows no active threat indicators but maintains elevated risk through blacklist listings. Recommend continued observation and potential blocking pending additional correlation with internal threat intelligence.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฎ๐Ÿ‡ณ India
Regionโ€”
CityNewark
Timezoneโ€”
Latitudeโ€”
Longitudeโ€”

๐Ÿข Ownership & Registration

OrganizationUMESH BAGHEL
ASNAS59162
Network NameUPIPL
CIDR Block43.225.68.0/22
RIRAPNIC
CountryIN
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 PurposeWeb Server
Network TierUnknown โ€” Insufficient routing data to classify
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpโ€”
443httpstcpโ€”
22sshtcp
Closed Ports25, 3389, 8080, 8443 (3 open / 7 scanned)
Serverlighttpd/1.4.39
HTTP Titleโ€”
SSH VersionSSH-2.0-dropbear <,{???gd?=T?|;???curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-gro

๐Ÿ” 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
0%
00
services
0%
00
ownership
0%
00
reputation
25%
11
geolocation
0%
00
Overall8%22
Coverage: 2/6 dimensions ยท Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-07-24 20:34:18 UTC
Last Seen2026-08-04 05:42:59 UTC
Profile Built2026-08-02 11:01:36 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.