IPDebrief

31.59.44.150

IP Intelligence Dossier
Your IP: 216.73.217.131
{ } JSON 🔧 Full Actions API
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

Thinking Process:

1. Analyze the Request:

* Role: IP intelligence analyst for IPDebrief (legitimate cybersecurity threat intelligence platform).

* Task: Generate an intelligence briefing for IP 31.59.44.150/32 based on the provided profile.

* Constraints: Concise, actionable threat intelligence narrative suitable for a SOC analyst, third person, past tense, use only provided data, no speculation, no disclaimers, no mention of internal tools.

* Input Data: A JSON-like profile containing

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

🌍 Geolocation

Country🇳🇱 Netherlands
RegionNorth Holland
CityAmsterdam
TimezoneEurope/Amsterdam
Latitude52.13
Longitude5.29

🏢 Ownership & Registration

OrganizationFarhad Soltani
ASNAS56971
Network NameCloudBackbone
CIDR Block31.59.44.0/23
RIRRIPE
CountryNL
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 Score0% (None)
SPF0/2 domains
DMARC0/2 domains
FCrDNSNot verified
DNSSECNot signed
CAANot configured
Domains Checked2 domains

☁️ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierUnknown — Insufficient routing data to classify
No specific classification

🔌 Services & Open Ports

PortServiceProtocolBanner
443httpstcp—
22sshtcpBanner detected
Closed Ports25, 80, 3389, 8080, 8443 (2 open / 7 scanned)
ServerWeb server detected
HTTP Title—

🔐 TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Issued by CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Self-signed: Yes
SANsinvalid2.invalid
Valid From2026-08-10T09:42:20+00:00
Valid Until2026-11-02T09:42:19+00:00

🛡️ Public Network Snapshot

Origin ASNAS56971
Network Prefix31.59.44.0/24
Route mappingFound
HSTSNot detected
CSPNot detected
HTTP/2Enabled

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
34%
29
routing
8%
11
services
32%
27
ownership
17%
23
reputation
16%
13
geolocation
17%
23
Overall21%1026
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) — 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: US, NL

📅 Observation Timeline 🔄 Live

First Seen2026-07-15 10:09:07 UTC
Last Seen2026-09-29 03:07:53 UTC
Profile Built2026-09-28 02:53:43 UTC
Data FreshnessLive
Signal Types24
Total Observations40
🔍 24 signal types · 40 observations collected
This report is generated from 24+ 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

❓ Frequently Asked Questions About 31.59.44.150

Who owns the IP address 31.59.44.150?

31.59.44.150 is registered to Farhad Soltani. The address falls within the 31.59.44.0/23 network block. Registration is held at RIPE.

Where is 31.59.44.150 located?

Geolocation data places 31.59.44.150 in Amsterdam, North Holland, Netherlands. The local time zone is Europe/Amsterdam. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 31.59.44.150 malicious or safe?

31.59.44.150 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.

What ports are open on 31.59.44.150?

Responsive ports observed on 31.59.44.150 include 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.

🏘️ Related IP Addresses

Nearby addresses in 31.59.44.0/23

Browse related networks

ℹ️ 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.