Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Long-established allocation (17y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Enterprise allocation +4
- Trust score 85 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- mx2.vpls.co.th
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 38400 s
- Reverse DNS last checked
- 2026-10-23 19:39 UTC
- Forward DNS last checked
- 2026-10-23 19:39 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-10-18 UTC0
issued.live's latest DNS data shows no domain resolving to this IP.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
Reverse-DNS changes between Oct 23, 2026 and Oct 23, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- mx2.vpls.co.th — since at least Oct 23, 2026 → present
- mx1.vpls.co.th — Oct 23, 2026 → Oct 23, 2026
- mx2.vpls.co.th — Oct 22, 2026 → Oct 23, 2026
- mx1.vpls.co.th — Oct 22, 2026 → Oct 22, 2026
- mx2.vpls.co.th — Oct 21, 2026 → Oct 22, 2026
- mx1.vpls.co.th — Oct 20, 2026 → Oct 21, 2026
- mx2.vpls.co.th — Oct 20, 2026 → Oct 20, 2026
- mx1.vpls.co.th — Oct 18, 2026 → Oct 20, 2026
- mx2.vpls.co.th — Oct 13, 2026 → Oct 18, 2026
- mx1.vpls.co.th — Oct 13, 2026 → Oct 13, 2026
- mx2.vpls.co.th — Oct 12, 2026 → Oct 13, 2026
- mx1.vpls.co.th — Oct 9, 2026 → Oct 12, 2026
- mx2.vpls.co.th — Oct 8, 2026 → Oct 9, 2026
- mx1.vpls.co.th — Oct 7, 2026 → Oct 8, 2026
- mx2.vpls.co.th — Oct 7, 2026 → Oct 7, 2026
- mx1.vpls.co.th — Oct 6, 2026 → Oct 7, 2026
- mx2.vpls.co.th — Oct 5, 2026 → Oct 6, 2026
- mx1.vpls.co.th — Oct 4, 2026 → Oct 5, 2026
- mx2.vpls.co.th — Oct 2, 2026 → Oct 4, 2026
- mx1.vpls.co.th — Sep 29, 2026 → Oct 2, 2026
- mx2.vpls.co.th — Sep 25, 2026 → Sep 29, 2026
- mx1.vpls.co.th — Aug 25, 2026 → Sep 25, 2026
- mx2.vpls.co.th — Aug 18, 2026 → Aug 25, 2026
- mx1.vpls.co.th — Jul 1, 2026 → Aug 18, 2026
- mx2.vpls.co.th — Jun 21, 2026 → Jul 1, 2026
- mx1.vpls.co.th — Jun 12, 2026 → Jun 21, 2026
Network Allocation for 110.34.221.5
- CIDR range
- 110.34.220.0/22
- IP range (int)
- 1,847,778,304 — 1,847,779,327
- Prefix length
- /22
- Organization
- Krypt Technologies
- ASN
- AS35908
- ASN name
- Krypt Technologies
- Location
- Thailand
- Coordinates
- 13.744200, 100.460800
- Accuracy radius
- 500 km
- Regional Internet Registry
- APNIC
- Allocated
- 2009-02-27
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-10-23 08:46:10
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | TH |
See the full history for 110.34.192.0/18.
Frequently Asked Questions
Who owns 110.34.221.5?
110.34.221.5 is allocated to Krypt Technologies (AS35908), registered in Thailand.
Where is 110.34.221.5 located?
The geolocation for 110.34.221.5 maps to Thailand based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 110.34.221.5 on?
110.34.221.5 belongs to the 110.34.220.0/22 network block announced by AS35908. This range contains 1,024 addresses.
Does 110.34.221.5 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
