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
- Active-threat / abuse risk −12
- Long-established allocation (18y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Isp allocation +5
- Trust score 74 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- blfmx02.bianlifeng.com
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 21600 s
- Reverse DNS last checked
- 2026-10-24 08:57 UTC
- Forward DNS last checked
- 2026-10-24 08:57 UTC
Forward DNS records for blfmx02.bianlifeng.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 120.133.18.137 | — | 600s |
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.
- blfmx02.bianlifeng.com — Oct 24, 2026 → present
- blfmx01.bianlifeng.com — Oct 22, 2026 → Oct 24, 2026
- blfmx02.bianlifeng.com — Oct 21, 2026 → Oct 22, 2026
- blfmx01.bianlifeng.com — Oct 20, 2026 → Oct 21, 2026
- blfmx02.bianlifeng.com — Oct 19, 2026 → Oct 20, 2026
- blfmx01.bianlifeng.com — Oct 18, 2026 → Oct 19, 2026
- blfmx02.bianlifeng.com — Oct 13, 2026 → Oct 18, 2026
- blfmx01.bianlifeng.com — Oct 12, 2026 → Oct 13, 2026
- blfmx02.bianlifeng.com — Oct 9, 2026 → Oct 12, 2026
- blfmx01.bianlifeng.com — Oct 7, 2026 → Oct 9, 2026
- blfmx02.bianlifeng.com — Oct 6, 2026 → Oct 7, 2026
- blfmx01.bianlifeng.com — Oct 4, 2026 → Oct 6, 2026
- blfmx02.bianlifeng.com — Oct 4, 2026 → Oct 4, 2026
- blfmx01.bianlifeng.com — Oct 3, 2026 → Oct 4, 2026
- blfmx02.bianlifeng.com — Oct 3, 2026 → Oct 3, 2026
- blfmx01.bianlifeng.com — Oct 1, 2026 → Oct 3, 2026
- blfmx02.bianlifeng.com — Oct 1, 2026 → Oct 1, 2026
- blfmx01.bianlifeng.com — Sep 29, 2026 → Oct 1, 2026
- blfmx02.bianlifeng.com — Sep 29, 2026 → Sep 29, 2026
- blfmx01.bianlifeng.com — Sep 28, 2026 → Sep 29, 2026
- blfmx02.bianlifeng.com — Aug 19, 2026 → Sep 28, 2026
- blfmx01.bianlifeng.com — Jul 7, 2026 → Aug 19, 2026
- blfmx02.bianlifeng.com — Jul 3, 2026 → Jul 7, 2026
- blfmx01.bianlifeng.com — Jun 28, 2026 → Jul 3, 2026
- blfmx02.bianlifeng.com — Jun 12, 2026 → Jun 28, 2026
Network Allocation for 120.133.18.135
- CIDR range
- 120.133.16.0/22
- IP range (int)
- 2,021,986,304 — 2,021,987,327
- Prefix length
- /22
- Organization
- China Unicom IP network
- ASN
- AS133119
- ASN name
- China Unicom IP network
- Location
- China
- Coordinates
- 34.773200, 113.722000
- Accuracy radius
- 1000 km
- Regional Internet Registry
- APNIC
- Allocated
- 2008-04-04
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-07-05 00:21:21
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 120.133.18.135?
120.133.18.135 is allocated to China Unicom IP network (AS133119), registered in China.
Where is 120.133.18.135 located?
The geolocation for 120.133.18.135 maps to China 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 120.133.18.135 on?
120.133.18.135 belongs to the 120.133.16.0/22 network block announced by AS133119. This range contains 1,024 addresses.
Does 120.133.18.135 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.
