IPDebrief

168.144.35.250

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.

Intelligence Briefing: IP 168.144.35.250/32

Overview:

The IP address 168.144.35.250/32 was observed with the following characteristics and behaviors. This briefing compiles data from various intelligence and network analysis tools to provide a comprehensive profile.

Observation History:

Domain Relationships:

Neighborhood Data:

Behavioral Indicators:

Threat Intelligence Summary:

- Implement network monitoring for traffic originating from or directed to this IP.

- Apply URL filtering to block access to domains resolved to this IP address.

- Conduct further investigation on co-located IPs for potential threat vectors.

- Consider engaging with the hosting provider for remediation actions if malicious activity is confirmed.

This intelligence should be used to enhance the organization's threat detection and response capabilities, ensuring proactive defense against potential threats associated with this IP address.

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

🌍 Geolocation

CountryπŸ‡ΈπŸ‡¬ Singapore
Regionβ€”
CitySingapore
TimezoneAsia/Singapore
Latitude1.35
Longitude103.82

🏒 Ownership & Registration

OrganizationDigitalOcean, LLC
ASNAS14061
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

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
22sshtcp
Closed Ports25, 3389, 8080, 8443 (3 open / 7 scanned)
Servernginx
HTTP Titleβ€”
SSH VersionSSH-2.0-OpenSSH_9.9

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
CN=168.144.35.250
Issued by CN=168.144.35.250
Self-signed: Yes
SANsNone
Valid From2026-06-12T07:32:31+00:00
Valid Until2036-06-09T07:32:31+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period3650 days
Serial Number67751AED2AE404EC3771640E26FB2A8227B3948C
ThumbprintD40C772851906A72B738823FEC82D531F697524E

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
30%
23
routing
8%
11
services
37%
23
ownership
20%
23
reputation
23%
12
geolocation
34%
23
Overall25%1015
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-24 18:40:08 UTC
Last Seen2026-06-29 00:23:53 UTC
Profile Built2026-06-29 06:26:15 UTC
Data FreshnessLive
Signal Types19
Total Observations20
πŸ” 19 signal types Β· 20 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.