IPDebrief

179.61.232.244

IP Intelligence Dossier
Your IP: 216.73.217.135
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

Threat Intelligence Briefing: IP 179.61.232.244/32

Overview:

The IP address 179.61.232.244/32 was analyzed to provide a comprehensive threat intelligence profile. The analysis incorporated various tools to gather data on its observation history, relationships, and neighborhood characteristics.

Observation History:

Relationships:

Neighborhood Data:

Actionable Recommendations:

1. Monitoring and Blocking: Implement continuous monitoring of traffic originating from and destined to 179.61.232.244/32. Consider adding it to a block list to prevent further malicious activity.

2. Anomaly Detection: Enhance anomaly detection systems to identify unusual traffic patterns associated with this IP, especially during peak malicious activity periods.

3. Incident Response Preparation: Prepare incident response teams for potential breaches involving this IP, focusing on rapid isolation and remediation strategies.

4. Threat Intelligence Sharing: Share findings with threat intelligence communities to aid in broader detection and mitigation efforts against the associated botnet infrastructure.

This briefing provides a factual overview based on observed data and should guide SOC teams in mitigating potential threats associated with IP 179.61.232.244/32.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNY
CityBuffalo
Timezoneβ€”
Latitude42.89
Longitude-78.88

🏒 Ownership & Registration

Organizationnetutils-mnt
ASNAS14670
Network Nameβ€”
CIDR Blockβ€”
RIRLACNIC
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
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
24%
23
routing
13%
11
services
8%
11
ownership
24%
23
reputation
22%
13
geolocation
27%
23
Overall20%914
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-08 17:17:45 UTC
Last Seen2026-06-26 18:10:50 UTC
Profile Built2026-06-25 08:46:31 UTC
Data FreshnessLive
Signal Types16
Total Observations17
πŸ” 16 signal types Β· 17 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.