160.16.131.175
Subject: Intelligence Briefing for 160.16.131.175/32
Analysis of the IP address 160.16.131.175/32 revealed a Low Risk reputation with a risk score of 0. The address was registered under ASN 9370, operated by the Japan Network Information Center (SAKURA-NET), within the 160.16.131.0/24 CIDR block. Geolocation data placed the infrastructure in Tokyo, Japan, with consensus across sources.
Threat intelligence feeds indicated no active malicious indicators, known campaigns, or blacklist associations. The address was identified as a Single-Service Host with a service purpose of Single-Service. Active services analysis confirmed an open SSH connection on port 22/tcp, utilizing OpenSSH 7.6p1. DNS resolution was forward confirmed to ne.jp, and reverse lookup resolved to tk2-401-41921.vs.sakura.ne.jp.
No evidence of abuse or attacker activity was present in the profile. SOC analysts should monitor standard traffic patterns associated with SAKURA-NET infrastructure, as no immediate containment or blocking actions were indicated by the
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Japan Network Information Center |
| ASN | AS9370 |
| Network Name | SAKURA-NET |
| CIDR Block | 160.16.131.0/24 |
| RIR | ARIN |
| Country | JP |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | tk2-401-41921.vs.sakura.ne.jp |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | tk2-401-41921.vs.sakura.ne.jp |
🔐 DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Single-Service Host |
| Network Tier | Tier 3 — Basic operator with some routing infrastructure |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS9370 |
| Network Prefix | 160.16.128.0/17 |
| Route mapping | Found |
| Certificates in transparency logs | 0 certificates |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 28% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 25% | 2 | 3 |
| ownership | 23% | 2 | 4 |
| reputation | 20% | 1 | 3 |
| geolocation | 23% | 2 | 4 |
| Overall | 21% | 10 | 19 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-12 08:51:07 UTC |
| Last Seen | 2026-09-03 11:53:53 UTC |
| Profile Built | 2026-09-03 11:58:49 UTC |
| Data Freshness | Live |
| Signal Types | 25 |
| Total Observations | 35 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 160.16.131.175
Who owns the IP address 160.16.131.175?
160.16.131.175 is registered to Japan Network Information Center. The address falls within the 160.16.131.0/24 network block. Registration is held at ARIN.
Where is 160.16.131.175 located?
Geolocation data places 160.16.131.175 in Tokyo, 13, Japan. The local time zone is Asia/Tokyo. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 160.16.131.175 malicious or safe?
160.16.131.175 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 160.16.131.175?
The reverse DNS (PTR) record for 160.16.131.175 is tk2-401-41921.vs.sakura.ne.jp. This hostname is forward-confirmed, meaning it resolves back to the same address.
What ports are open on 160.16.131.175?
Responsive ports observed on 160.16.131.175 include 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.