218.253.206.62
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 (24y) +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)
- ns1.j2global.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 900 s
- Reverse DNS last checked
- 2026-10-23 06:52 UTC
Forward DNS records for ns1.j2global.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 127.0.0.1 | — | 16901s |
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 21, 2026 and Oct 23, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- ns1.j2global.com — since at least Oct 23, 2026 → present
- ns2.j2global.com — Oct 21, 2026 → Oct 23, 2026
- ns5.j2global.com — Oct 21, 2026 → Oct 21, 2026
- ns1.j2global.com — Oct 20, 2026 → Oct 21, 2026
- ns5.j2global.com — Oct 20, 2026 → Oct 20, 2026
- ns2.j2global.com — Oct 19, 2026 → Oct 20, 2026
- ns5.j2global.com — Oct 18, 2026 → Oct 19, 2026
- ns2.j2global.com — Oct 18, 2026 → Oct 18, 2026
- ns1.j2global.com — Oct 17, 2026 → Oct 18, 2026
- ns2.j2global.com — Oct 16, 2026 → Oct 17, 2026
- ns1.j2global.com — Oct 16, 2026 → Oct 16, 2026
- ns2.j2global.com — Oct 14, 2026 → Oct 16, 2026
- ns1.j2global.com — Oct 13, 2026 → Oct 14, 2026
- ns2.j2global.com — Oct 13, 2026 → Oct 13, 2026
- ns1.j2global.com — Oct 13, 2026 → Oct 13, 2026
- ns5.j2global.com — Oct 12, 2026 → Oct 13, 2026
- ns1.j2global.com — Oct 11, 2026 → Oct 12, 2026
- ns2.j2global.com — Oct 11, 2026 → Oct 11, 2026
- ns5.j2global.com — Oct 11, 2026 → Oct 11, 2026
- ns1.j2global.com — Oct 10, 2026 → Oct 11, 2026
- ns2.j2global.com — Oct 9, 2026 → Oct 10, 2026
- ns5.j2global.com — Oct 9, 2026 → Oct 9, 2026
- ns1.j2global.com — Oct 8, 2026 → Oct 9, 2026
- ns5.j2global.com — Oct 8, 2026 → Oct 8, 2026
- ns1.j2global.com — Oct 7, 2026 → Oct 8, 2026
- ns2.j2global.com — Oct 6, 2026 → Oct 7, 2026
- ns5.j2global.com — Oct 6, 2026 → Oct 6, 2026
- ns1.j2global.com — Oct 6, 2026 → Oct 6, 2026
- localhost — Oct 5, 2026 → Oct 6, 2026
- ns1.j2global.com — Oct 4, 2026 → Oct 5, 2026
- ns2.j2global.com — Oct 4, 2026 → Oct 4, 2026
- ns5.j2global.com — Oct 3, 2026 → Oct 4, 2026
- no PTR — Oct 3, 2026 → Oct 3, 2026
- ns5.j2global.com — Oct 3, 2026 → Oct 3, 2026
- ns2.j2global.com — Oct 2, 2026 → Oct 3, 2026
- ns5.j2global.com — Oct 2, 2026 → Oct 2, 2026
- ns2.j2global.com — Oct 1, 2026 → Oct 2, 2026
- ns5.j2global.com — Oct 1, 2026 → Oct 1, 2026
- ns2.j2global.com — Sep 30, 2026 → Oct 1, 2026
- ns1.j2global.com — Sep 29, 2026 → Sep 30, 2026
- ns5.j2global.com — Sep 29, 2026 → Sep 29, 2026
- ns2.j2global.com — Sep 28, 2026 → Sep 29, 2026
- ns5.j2global.com — Sep 27, 2026 → Sep 28, 2026
- ns2.j2global.com — Sep 27, 2026 → Sep 27, 2026
- ns1.j2global.com — Sep 26, 2026 → Sep 27, 2026
- ns2.j2global.com — Sep 26, 2026 → Sep 26, 2026
- ns1.j2global.com — Sep 25, 2026 → Sep 26, 2026
- ns5.j2global.com — Aug 25, 2026 → Sep 25, 2026
- ns2.j2global.com — Aug 24, 2026 → Aug 25, 2026
- ns5.j2global.com — Aug 18, 2026 → Aug 24, 2026
- ns2.j2global.com — Aug 18, 2026 → Aug 18, 2026
- ns1.j2global.com — Jul 4, 2026 → Aug 18, 2026
- ns5.j2global.com — Jun 30, 2026 → Jul 4, 2026
- ns1.j2global.com — Jun 26, 2026 → Jun 30, 2026
- ns2.j2global.com — Jun 14, 2026 → Jun 26, 2026
- ns1.j2global.com — Jun 10, 2026 → Jun 14, 2026
Network Allocation for 218.253.206.62
- CIDR range
- 218.253.206.0/24
- IP range (int)
- 3,674,066,432 — 3,674,066,687
- Prefix length
- /24
- Organization
- HKBN Enterprise Solutions HK Limited
- ASN
- AS9381
- ASN name
- HKBN Enterprise Solutions HK Limited
- Location
- Hong Kong
- Coordinates
- 22.257800, 114.165700
- Accuracy radius
- 1000 km
- Regional Internet Registry
- APNIC
- Allocated
- 2002-08-08
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-10-04 08:40:25
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 | — | HK |
See the full history for 218.252.0.0/15.
Frequently Asked Questions
Who owns 218.253.206.62?
218.253.206.62 is allocated to HKBN Enterprise Solutions HK Limited (AS9381), registered in Hong Kong.
Where is 218.253.206.62 located?
The geolocation for 218.253.206.62 maps to Hong Kong 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 218.253.206.62 on?
218.253.206.62 belongs to the 218.253.206.0/24 network block announced by AS9381. This range contains 256 addresses.
Does 218.253.206.62 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.
