101.108.220.159
I'm unable to complete this intelligence briefing at this time. All API requests to IPDebrief services are timing out, preventing retrieval of the required profile, history, relationships, and neighborhood data for IP 101.108.220.159.
To proceed with generating a comprehensive threat intelligence briefing, the IPDebrief API service needs to be operational and accessible. Please verify:
1. API connectivity and service availability
2. Network/firewall rules allowing outbound connections to IPDebrief endpoints
3. API rate limits or quota constraints that may be causing timeouts
Once the connectivity issue is resolved, I can execute the full intelligence gathering sequence and produce the requested SOC-ready threat briefing.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IRT-TOT-TH |
| ASN | AS23969 |
| Network Name | totnet |
| CIDR Block | 101.108.0.0/16 |
| RIR | APNIC |
| Country | th |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | node-17kv.pool-101-108.dynamic.nt-isp.net |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | node-17kv.pool-101-108.dynamic.nt-isp.netnode-17kv.pool-101-108.dynamic.nt-isp.net |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Not configured |
| FCrDNS | 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 | AS23969 |
| Network Prefix | 101.108.220.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 16% | 4 | 4 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-10 14:00:09 UTC |
| Last Seen | 2026-08-27 09:05:35 UTC |
| Profile Built | 2026-08-29 04:52:40 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 20 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 101.108.220.159
Who owns the IP address 101.108.220.159?
101.108.220.159 is registered to IRT-TOT-TH. The address falls within the 101.108.0.0/16 network block. Registration is held at APNIC.
Where is 101.108.220.159 located?
Geolocation data places 101.108.220.159 in Phuket, Phuket, Thailand. The local time zone is Asia/Bangkok. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 101.108.220.159 malicious or safe?
101.108.220.159 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 101.108.220.159?
The reverse DNS (PTR) record for 101.108.220.159 is node-17kv.pool-101-108.dynamic.nt-isp.net. This hostname is forward-confirmed, meaning it resolves back to the same address.