IPDebrief

186.64.71.36

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.

IP Intelligence Briefing: 186.64.71.36

Date: 2026-06-06

---

**1. Core Profile**

- HTTP: Lighttpd 1.4.39 (302 redirect)

- SSH: Dropbear 2026-05-29 (banner: `SSH-2.0-dropbear`)

- TLS: No certificate detected

---

**2. Observation History**

- HTTP server responded with 302 status code (likely redirect).

- SSH service active with Dropbear, no TLS encryption.

- Geolocation data inconsistent (geoPlausible: false, 1500km accuracy radius).

- PTR record: `host36.186-64-71.nodosud.com.ar`

- No SPF/DKIM records, no email authentication.

---

**3. Network Relationships**

- Linked to `host36.186-64-71.nodosud.com.ar` (multiple PTR records).

- AS27953 (NODOSUD S.A) peered with AS6939 and AS3356.

- No RPKI invalidations or IRR inconsistencies.

---

**4. Subnet Neighborhood**

- Abuse Density: 14.29% (moderate risk).

- High-Risk Neighbors:

- 186.64.71.55 (risk score 65).

- Active IPs: 1 out of 7 siblings (14.29%).

- Threat Siblings: 1 (14.29%).

---

**5. Threat Assessment**

- SSH without TLS encryption may expose credentials.

- No TLS certificate for HTTP service (potential downgrade attacks).

- One neighbor (186.64.71.55) shows higher risk; investigate for potential botnet or compromised hosts.

- Inconsistent geolocation data may indicate spoofing or misconfigured DNS.

---

**6. Recommendations**

1. Monitor SSH Traffic: Enforce TLS for SSH (e.g., switch to OpenSSH with TLS).

2. Verify TLS Configuration: Ensure HTTPS services use valid certificates.

3. Subnet Scanning: Prioritize 186.64.71.55 for threat analysis.

4. DNS Validation: Confirm PTR records for `host36.186-64-71.nodosud.com.ar` to avoid misattribution.

---

Source: IPDebrief Threat Intelligence Platform | Updated: 2026-06-06

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฆ๐Ÿ‡ท Argentina
RegionCordoba
CityMorrison
Timezoneโ€”
Latitude-32.60
Longitude-62.84

๐Ÿข Ownership & Registration

OrganizationNODOSUD S.A
ASNAS27953
Network Name186.64.64.0 - 186.64.95.255
CIDR Block186.64.64.0/19
RIRLACNIC
CountryAR
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTRhost36.186-64-71.nodosud.com.ar
Forward ConfirmedNo โ€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnameshost36.186-64-71.nodosud.com.ar

๐Ÿ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureUnknown
Service PurposeMulti-Service Host
Network TierTier 3 โ€” Basic operator with some routing infrastructure
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpโ€”
22sshtcp
Closed Ports25, 443, 3389, 8080, 8443 (2 open / 7 scanned)
Serverlighttpd/1.4.39
HTTP Titleโ€”
SSH VersionSSH-2.0-dropbear <$|?????x??????N??curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-gr

๐Ÿ” 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%
24
routing
33%
24
services
27%
23
ownership
30%
34
reputation
22%
13
geolocation
19%
22
Overall26%1220
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-13 19:04:21 UTC
Last Seen2026-06-06 23:36:23 UTC
Profile Built2026-06-06 23:53:33 UTC
Data FreshnessLive
Signal Types24
Total Observations29
๐Ÿ” 24 signal types ยท 29 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

โ„น๏ธ 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.