IPDebrief

216.151.137.110

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.

Threat Intelligence Briefing: IP 216.151.137.110/32

Summary:

The IP address 216.151.137.110, observed across multiple security tools, has shown consistent patterns and relationships that are relevant to the Security Operations Center (SOC) team. The IP is associated with legitimate services but has had historical associations with suspicious activities, necessitating closer monitoring.

Observation History:

Behavioral Analysis:

Neighborhood Data:

Relationships:

Actionable Recommendations:

1. Enhanced Monitoring: Implement additional monitoring for traffic originating from this IP address. Focus on identifying patterns consistent with data exfiltration or command and control activity.

2. User Education: Increase awareness campaigns about phishing threats, particularly those involving emails from domains associated with this IP.

3. Threat Intelligence Integration: Continuously update threat intelligence feeds with the latest data on this IP address to ensure timely detection of any emerging threats.

4. Collaboration with ISP: Engage with AT&T to report suspicious activities and collaborate on mitigating potential threats associated with this IP address.

This intelligence briefing provides a comprehensive overview of IP 216.151.137.110/32, highlighting its legitimate usage, historical associations with malicious activities, and recommended actions for SOC analysts.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-NY
CityNew York
Timezoneβ€”
Latitude37.75
Longitude-97.82

🏒 Ownership & Registration

OrganizationCisco Webex LLC
ASNAS13445
Network Nameβ€”
CIDR Blockβ€”
RIRARIN
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
28%
23
routing
8%
11
services
8%
11
ownership
20%
23
reputation
30%
13
geolocation
24%
23
Overall20%914
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:05:08 UTC
Last Seen2026-06-26 18:12:06 UTC
Profile Built2026-06-27 01:32:41 UTC
Data FreshnessLive
Signal Types19
Total Observations47
πŸ” 19 signal types Β· 47 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 πŸ”§ 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.