IPDebrief

141.11.36.82

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 for IP 141.11.36.82/32

Summary:

The IP address 141.11.36.82/32 was analyzed for its threat profile, observation history, relationships, and neighborhood data. The following intelligence provides a detailed overview based on available data:

Observation History:

Threat Profile:

Relationships:

Neighborhood Data:

Actionable Recommendations:

1. Monitoring: Implement enhanced monitoring of traffic originating from this IP and related IPs within the subnet. Focus on detecting unusual patterns or spikes in activity.

2. Blocking: Consider blocking traffic from 141.11.36.82/32 and its associated IPs at the firewall level to prevent potential threats from reaching the network.

3. Awareness: Increase cybersecurity awareness among employees, particularly regarding phishing attempts. Educate them on recognizing suspicious emails and websites.

4. Incident Response: Prepare an incident response plan for potential breaches involving this IP. Ensure that SOC teams are ready to investigate and mitigate any threats quickly.

This intelligence briefing provides a comprehensive overview of the threat landscape associated with IP 141.11.36.82/32, enabling SOC analysts to make informed decisions in defending their networks.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionCampania
CityNaples
Timezoneβ€”
Latitude40.84
Longitude14.27

🏒 Ownership & Registration

OrganizationPrivate Customer
ASNAS137409
Network Nameβ€”
CIDR Blockβ€”
RIRRIPE
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
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
27%
23
routing
13%
11
services
19%
22
ownership
27%
23
reputation
22%
13
geolocation
27%
23
Overall22%1015
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-14 13:23:33 UTC
Last Seen2026-06-07 05:17:15 UTC
Profile Built2026-06-07 05:20:14 UTC
Data FreshnessLive
Signal Types17
Total Observations17
πŸ” 17 signal types Β· 17 observations collected
This report is generated from 17+ 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.