IPDebrief

196.0.119.218

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

Summary:

This intelligence briefing provides a detailed profile of the IP address 196.0.119.218/32. The analysis includes observation history, relationships, and neighborhood data, intended to assist SOC teams and network defenders in understanding potential security implications.

Profile:

- The IP has been observed engaging in traffic patterns consistent with both standard web hosting activities and occasional spikes in traffic volume, potentially indicative of compromised or malicious use.

- DNS records associated with this IP have shown frequent changes, suggesting dynamic usage possibly related to hosting services for multiple clients or short-lived content.

Relationships:

Neighborhood Data:

Actionable Insights:

Conclusion:

The IP address 196.0.119.218/32 has been associated with multiple indicators of compromise and malicious activities. SOC teams should prioritize monitoring and defensive measures to protect against potential threats originating from this IP.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionCA
CitySan Jose
Timezoneβ€”
Latitude0.32
Longitude32.57

🏒 Ownership & Registration

OrganizationKevin Mugaya Francis
ASNAS21491
Network NameORG-UTL1-AFRINIC
CIDR Block196.0.0.0/16
RIRAFRINIC
CountryUG
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 PurposeWeb Server
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
22sshtcp
Closed Ports25, 3389, 8080, 8443 (3 open / 7 scanned)
Serverlighttpd/1.4.54
HTTP Titleβ€”
SSH VersionSSH-2.0-dropbear T ???k?C\l??9_=?curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-grou

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
E=support@ubnt.com, CN=UBNT-24:5A:4C:0C:12:CE, OU=Technical Support, O=Ubiquiti Networks Inc., L=San Jose, S=CA, C=US
Issued by E=support@ubnt.com, CN=UBNT-24:5A:4C:0C:12:CE, OU=Technical Support, O=Ubiquiti Networks Inc., L=San Jose, S=CA, C=US
Self-signed: Yes
SANsUBNT-24:5A:4C:0C:12:CE
Valid From2019-01-01T00:00:00+00:00
Valid Until2038-01-01T00:00:00+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period6940 days
Serial NumberB0D4BB9B
ThumbprintE7F9E51EE887B2ACA2960D66C4ABED348E799800

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
24%
23
routing
13%
11
services
28%
23
ownership
19%
22
reputation
22%
13
geolocation
13%
11
Overall20%913
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-10 10:13:36 UTC
Last Seen2026-06-26 00:44:09 UTC
Profile Built2026-06-26 01:02:27 UTC
Data FreshnessLive
Signal Types18
Total Observations18
πŸ” 18 signal types Β· 18 observations collected
This report is generated from 18+ 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.