163.223.136.34
Intelligence analysis classified IP 163.223.136.34 as a moderate-risk host (Score: 40) associated with ASN 137655 (IRT-ANGELB-IN) in Abohar, Punjab, India. The address operated within a subnet flagged as high_abuse (163.223.136.0/24), which contained four threat siblings among seven total peers. While the host presented no open services or enumeration strikes, it appeared on one DNS blacklist with a total listing count of eight. Operational recommendations advised rate-limiting traffic at a medium severity level. Observations were recorded between 13 July and 14 September 2026, with DNS hygiene scoring fair due to the absence of DMARC policies.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IRT-ANGELB-IN |
| ASN | AS137655 |
| Network Name | ANGELB |
| CIDR Block | 163.223.136.0/24 |
| RIR | APNIC |
| Country | IN |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | 34-136-223-163.angelbroadband.com |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 34-136-223-163.angelbroadband.com |
🔐 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 | 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 | AS137655 |
| Network Prefix | 163.223.136.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 31% | 2 | 6 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 27% | 2 | 6 |
| reputation | 16% | 1 | 3 |
| geolocation | 17% | 2 | 3 |
| Overall | 18% | 10 | 21 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-13 09:17:05 UTC |
| Last Seen | 2026-09-14 01:22:38 UTC |
| Profile Built | 2026-09-14 02:07:32 UTC |
| Data Freshness | Live |
| Signal Types | 24 |
| Total Observations | 37 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 163.223.136.34
Who owns the IP address 163.223.136.34?
163.223.136.34 is registered to IRT-ANGELB-IN. The address falls within the 163.223.136.0/24 network block. Registration is held at APNIC.
Where is 163.223.136.34 located?
Geolocation data places 163.223.136.34 in Abohar, Punjab, India. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 163.223.136.34 malicious or safe?
163.223.136.34 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 163.223.136.34?
The reverse DNS (PTR) record for 163.223.136.34 is 34-136-223-163.angelbroadband.com. This hostname is not forward-confirmed, so it should be treated as a weak signal.