# IP Intelligence Briefing: 64.31.36.36
## Executive Summary
IP 64.31.36.36 is classified as Low Risk with a risk score of 20. The address is owned by Limestone Networks, Inc. and shows no active threat indicators. Recommended security posture: Monitor but no blocking action required.
## Ownership and Registration
- ASN: 46475 (Limestone Networks, Inc.)
- Organization: LIMESTONE-NETWORKS
- CIDR Block: 64.31.0.0/18
- RIR: ARIN
- Abuse Contact: Available via RDAP
## Geolocation
- Country: United States (US)
- Region: Oregon
- City: Portland
- Note: Geo validation flagged with RTT anomaly (94ms vs 162ms minimum possible for 8098km distance), indicating geolocation data may be inconsistent.
## Network Role Classification
- Status: Firewalled / No Services
- Classification: Not a provider, CDN, VPN, proxy, hosting, mobile, residential, bogon, or anycast infrastructure
- Tor Exit: No
- Known Attacker: No
- Spam Source: No
## Threat Indicators
- Blacklist Count: 0
- Abuse Confidence Score: None
- Known Campaigns: None
- Threat Feeds: Empty
- DNSBL Listed: 0/8 total lists
## DNS Analysis
- PTR Hostname: 36-36-31-64.static.reverse.lstn.net
- Domain: lstn.net
- Forward Resolution: Not confirmed
- SPF Record: Present
- DMARC Record: Not present
- Hosted Domain Count: 0
## Services and Open Ports
- Open Ports: None detected
- TLS Certificate: None
- HTTP Title/Server Banner: None detected
## Neighborhood Analysis (64.31.36.0/24)
- Subnet Classification: Clean
- Abuse Density: 0
- Total Siblings: 11
- Active Siblings: 0
- Threat Siblings: 0
Neighbor Risk Distribution:
- High Risk: 0
- Medium Risk: 0
- Low Risk: 10
Notable neighbor IPs showing elevated risk (score 20-25): 64.31.36.227, 64.31.36.88, 64.31.36.164. These IPs should be monitored but do not indicate subnet-wide compromise.
## Historical Observations
Analysis of 20 recent observations shows:
- Consistent clean classification across all recent signals
- Zero ownership changes detected
- No persistent malicious activity indicators
- Abuse density remains at 0 throughout observation period
- Threat observation count: 0
## Relationships
- Network Associations: Multiple entries linked to LIMESTONE-NETWORKS
- DNS Associations: 4 relationships to 36-36-31-64.static.reverse.lstn.net
- No external entity correlations detected
## Recommended Security Actions
- Action: Monitor but no blocking recommended
- Risk Profile: Low risk (20) with no active threat indicators
- Firewall Rules: No specific rules generated due to low risk profile
- Disposition: Allow with standard logging and monitoring
## Intelligence Assessment
IP 64.31.36.36 presents minimal security risk. The address is owned by a legitimate hosting provider (Limestone Networks, Inc.) and shows no indicators of malicious activity. The subnet environment is clean with zero abuse density. No immediate blocking or mitigating actions are warranted. Continue standard monitoring procedures.
---
*Intel generated by IPDebrief threat intelligence platform*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Limestone Networks, Inc. |
| ASN | AS46475 |
| Network Name | LIMESTONE-NETWORKS |
| CIDR Block | 64.31.0.0/18 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | 36-36-31-64.static.reverse.lstn.net |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 36-36-31-64.static.reverse.lstn.net |
🔐 DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Present |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| 8080 | http-alt | tcp | — |
| 3389 | rdp | tcp | — |
| Closed Ports | 25, 80, 8443 (4 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS46475 |
| Network Prefix | 64.31.36.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 12% | 2 | 2 |
| routing | 8% | 1 | 1 |
| services | 17% | 2 | 3 |
| ownership | 17% | 2 | 3 |
| reputation | 8% | 1 | 2 |
| geolocation | 25% | 2 | 4 |
| Overall | 15% | 10 | 15 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-14 15:51:23 UTC |
| Last Seen | 2026-09-02 04:38:03 UTC |
| Profile Built | 2026-09-02 04:44:49 UTC |
| Data Freshness | Live |
| Signal Types | 24 |
| Total Observations | 29 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 64.31.36.36
Who owns the IP address 64.31.36.36?
64.31.36.36 is registered to Limestone Networks, Inc.. The address falls within the 64.31.0.0/18 network block. Registration is held at ARIN.
Where is 64.31.36.36 located?
Geolocation data places 64.31.36.36 in Portland, Oregon, United States. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 64.31.36.36 malicious or safe?
64.31.36.36 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 64.31.36.36?
The reverse DNS (PTR) record for 64.31.36.36 is 36-36-31-64.static.reverse.lstn.net. This hostname is not forward-confirmed, so it should be treated as a weak signal.
What ports are open on 64.31.36.36?
Responsive ports observed on 64.31.36.36 include 443, 22, 8080, 3389. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.