36.255.6.22
IP address 36.255.6.22 was registered to Network Administrator under ASN 24186 (RAILTEL-IN) within the 36.255.4.0/22 block in Bengaluru, Karnataka, India. The system assigned a Low Risk reputation with a risk score of 25. No known threat indicators, campaigns, or spam sources were associated with the address, and it was not identified as a Tor exit node. While the overview indicated zero blacklist entries, control plane data recorded a single listing among eight total DNSBL checks. Service scans detected no open ports, HTTP headers, or TLS certificates, with the service purpose classified as Firewalled / No Services. Reverse DNS resolution failed, and no domains were hosted. DNSSEC validation was confirmed valid. Route stability was flagged as false, though no route changes occurred in the preceding 30 days.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Network Administrator |
| ASN | AS24186 |
| Network Name | RAILTEL-IN |
| CIDR Block | 36.255.4.0/22 |
| RIR | APNIC |
| Country | IN |
| 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 | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS24186 |
| Network Prefix | 36.255.6.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 17% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 20% | 1 | 3 |
| geolocation | 17% | 2 | 3 |
| Overall | 15% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-20 12:28:30 UTC |
| Last Seen | 2026-09-01 19:06:18 UTC |
| Profile Built | 2026-09-01 19:13:05 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 36.255.6.22
Who owns the IP address 36.255.6.22?
36.255.6.22 is registered to Network Administrator. The address falls within the 36.255.4.0/22 network block. Registration is held at APNIC.
Where is 36.255.6.22 located?
Geolocation data places 36.255.6.22 in Bengaluru, Karnataka, India. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 36.255.6.22 malicious or safe?
36.255.6.22 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.