IPDebrief

74.80.182.88

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: 74.80.182.88

## Executive Summary

Risk Assessment: Moderate Risk (Score: 40/100)

Status: Active Threat Indicator β€” Listed on 8 DNSBLs with high severity

Recommendation: Block at perimeter; monitor for lateral movement within /24 subnet

---

## Infrastructure Profile

AttributeValue
**Organization**Cyberzone S.A.
**ASN**13737 (CZ-MCI1-IPV4)
**Location**Kansas City, MO, US
**CIDR Block**74.80.182.64/26
**Network Role**Single-Service Host
**Open Services**TCP/8443 (https-alt)

## Threat Indicators

## Neighborhood Analysis (74.80.182.0/24)

Key neighbors include:

## Observed Behavior

## Recommended Security Actions

Firewall Rules

```bash

# iptables

iptables -A INPUT -s 74.80.182.88 -j DROP

# nftables

nft add rule inet filter input ip saddr 74.80.182.88 drop

```

WAF Rules

```nginx

# nginx

deny 74.80.182.88;

# Cloudflare WAF

Block IP: 74.80.182.88 (Risk Score: 40)

# AWS WAF

Block: 74.80.182.88/32

```

## SOC Analyst Notes

1. Subnet-Wide Risk: This IP belongs to a high-abuse subnet where 7 of 8 neighboring IPs are flagged as threats. Consider implementing subnet-based blocking policies for the entire /24.

2. Blacklist Presence: Multiple DNSBL listings with high severity indicate prior abuse history.

3. Service Exposure: TCP/8443 (https-alt) is open β€” verify if this is legitimate application traffic or potential command-and-control channel.

4. No Direct Threat Indicators: Despite moderate risk score, no direct threat indicators (tor, VPN, proxy, etc.) were observed on this specific IP.

## Mitigation Priority

High β€” Due to high-abuse subnet classification and multiple blacklist listings, recommend blocking at network perimeter and monitoring inbound traffic patterns from the 74.80.182.0/24 range.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionMO
CityKansas City
Timezoneβ€”
Latitude39.15
Longitude-94.57

🏒 Ownership & Registration

OrganizationCyberzone S.A.
ASNAS13737
Network NameCZ-MCI1-IPV4
CIDR Block74.80.182.64/26
RIRARIN
CountryUnited States
Abuse Contactβ€”

🌐 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 PurposeSingle-Service Host
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
8443https-alttcpβ€”
Closed Ports22, 25, 80, 443, 3389, 8080 (1 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
22%
24
routing
17%
23
services
12%
22
ownership
22%
33
reputation
19%
13
geolocation
19%
22
Overall18%1217
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-09 05:26:22 UTC
Last Seen2026-06-25 14:10:40 UTC
Profile Built2026-06-25 14:15:56 UTC
Data FreshnessLive
Signal Types24
Total Observations24
πŸ” 24 signal types Β· 24 observations collected
This report is generated from 24+ 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.