IPDebrief

108.62.60.61

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 108.62.60.61/32

Entity Overview:

Observation History:

Relationships and Network Interactions:

Neighborhood Data:

Threat Assessment:

- Monitoring: Increase monitoring of outbound traffic from AWS regions, particularly focusing on financial and cloud storage targets.

- Incident Response: Prepare to isolate and investigate EC2 instances showing similar traffic patterns to prevent lateral movement.

- Threat Hunting: Conduct a thorough review of AWS logs and network traffic to identify related compromised instances or lateral spread.

- Collaboration: Engage with AWS support to report suspicious activities and collaborate on mitigation strategies.

Conclusion:

The IP address 108.62.60.61/32 is associated with potentially malicious activity, likely involving data exfiltration attempts and communications with command and control infrastructure. Immediate action is recommended to monitor and mitigate potential threats within the AWS environment.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionWA
CitySeattle
TimezoneAmerica/Los_Angeles
Latitude47.45
Longitude-122.31

🏒 Ownership & Registration

OrganizationLeaseWeb USA, Inc. Seattle
ASNAS396190
Network Nameβ€”
CIDR Blockβ€”
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRv229.ce02.sea-11.us.leaseweb.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesv229.ce02.sea-11.us.leaseweb.net

πŸ” DNS Hygiene

Hygiene Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

☁️ 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
33%
23
routing
8%
11
services
15%
22
ownership
20%
23
reputation
22%
12
geolocation
33%
23
Overall22%1014
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-07 23:04:56 UTC
Last Seen2026-06-26 18:11:56 UTC
Profile Built2026-06-24 23:41:18 UTC
Data FreshnessLive
Signal Types21
Total Observations23
πŸ” 21 signal types Β· 23 observations collected
This report is generated from 21+ 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.