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 (25y) +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.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- vcsa.syseng.metconnect.net
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 21600 s
- Reverse DNS last checked
- 2026-10-25 16:02 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-24 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.
- vcsa.syseng.metconnect.net — Oct 25, 2026 → present
- vcsa.metconnect.net — Oct 24, 2026 → Oct 25, 2026
- vcsa.syseng.metconnect.net — Oct 23, 2026 → Oct 24, 2026
- vcsa.metconnect.net — Oct 21, 2026 → Oct 23, 2026
- vcsa.syseng.metconnect.net — Oct 20, 2026 → Oct 21, 2026
- vcsa.metconnect.net — Oct 19, 2026 → Oct 20, 2026
- vcsa.syseng.metconnect.net — Oct 17, 2026 → Oct 19, 2026
- vcsa.metconnect.net — Oct 16, 2026 → Oct 17, 2026
- vcsa.syseng.metconnect.net — Oct 15, 2026 → Oct 16, 2026
- vcsa.metconnect.net — Oct 14, 2026 → Oct 15, 2026
- vcsa.syseng.metconnect.net — Oct 12, 2026 → Oct 14, 2026
- vcsa.metconnect.net — Oct 11, 2026 → Oct 12, 2026
- vcsa.syseng.metconnect.net — Oct 10, 2026 → Oct 11, 2026
- vcsa.metconnect.net — Oct 8, 2026 → Oct 10, 2026
- vcsa.syseng.metconnect.net — Oct 7, 2026 → Oct 8, 2026
- vcsa.metconnect.net — Oct 5, 2026 → Oct 7, 2026
- vcsa.syseng.metconnect.net — Oct 3, 2026 → Oct 5, 2026
- vcsa.metconnect.net — Sep 27, 2026 → Oct 3, 2026
- vcsa.syseng.metconnect.net — Sep 24, 2026 → Sep 27, 2026
- vcsa.metconnect.net — Jun 12, 2026 → Sep 24, 2026
Network Allocation for 216.194.0.142
- CIDR range
- 216.194.0.0/22
- IP range (int)
- 3,636,592,640 — 3,636,593,663
- Prefix length
- /22
- Organization
- MetTel
- ASN
- AS16524
- ASN name
- MetTel
- Location
- Houston, Texas, United States
- Coordinates
- 29.713300, -95.480400
- Accuracy radius
- 1000 km
- Postal code
- 77081
- Regional Internet Registry
- ARIN
- Allocated
- 2001-01-24
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-25 05:27:57
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 216.194.0.142?
216.194.0.142 is allocated to MetTel (AS16524), registered in Houston, United States.
Where is 216.194.0.142 located?
The geolocation for 216.194.0.142 maps to Houston, United States 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 216.194.0.142 on?
216.194.0.142 belongs to the 216.194.0.0/22 network block announced by AS16524. This range contains 1,024 addresses.
Does 216.194.0.142 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.
