135.136.136.9
IP 135.136.136.9/32 was identified as a Low Risk asset with a risk score of 25. The address belongs to ASN 931 (Krixe Admin) and is geolocated to Canary Wharf, England, GB. Threat analysis indicated no known campaigns, zero blacklist hits, and no association with spam sources, Tor exit nodes, or known attackers. The network role was classified as a Single-Service Host. Service scanning detected an open port on TCP 3389 (RDP) with no associated TLS certificates or HTTP titles. DNS resolution showed no PTR hostnames and zero forward resolutions. Route stability was marked as false, and no specific actions were generated for this profile.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Krixe Admin |
| ASN | AS931 |
| Network Name | K135136136024 |
| CIDR Block | 135.136.136.0/24 |
| RIR | ARIN |
| Country | GB |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Single-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 3389 | rdp | tcp | — |
| Closed Ports | 22, 25, 80, 443, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS931 |
| Network Prefix | 135.136.136.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 34% | 2 | 5 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 33% | 1 | 5 |
| geolocation | 17% | 2 | 3 |
| Overall | 20% | 10 | 19 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-18 11:33:50 UTC |
| Last Seen | 2026-09-05 17:41:45 UTC |
| Profile Built | 2026-09-05 17:53:12 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 29 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 135.136.136.9
Who owns the IP address 135.136.136.9?
135.136.136.9 is registered to Krixe Admin. The address falls within the 135.136.136.0/24 network block. Registration is held at ARIN.
Where is 135.136.136.9 located?
Geolocation data places 135.136.136.9 in Canary Wharf, England, United Kingdom. The local time zone is Europe/London. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 135.136.136.9 malicious or safe?
135.136.136.9 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 ports are open on 135.136.136.9?
Responsive ports observed on 135.136.136.9 include 3389. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.