80.90.160.54
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
- Forward-confirmed reverse DNS (FCrDNS) +10
- Long-established allocation (25y) +6
- Not on any threat blocklist +5
- Mobile allocation +2
- Trust score 88 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ns3.jdcs.jo
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-10-28 02:50 UTC
- Forward DNS last checked
- 2026-10-28 02:50 UTC
Forward DNS records for ns3.jdcs.jo
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 80.90.160.54 | — | 172800s |
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-25 UTC16
Registrable domains (like example.com) with at least one name resolving to this IP — updated daily from issued.live's DNS data.
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.
- ns3.jdcs.jo — Oct 25, 2026 → present
- ns4.jdcs.jo — Oct 23, 2026 → Oct 25, 2026
- ns3.jdcs.jo — Oct 22, 2026 → Oct 23, 2026
- ns4.jdcs.jo — Oct 21, 2026 → Oct 22, 2026
- ns3.jdcs.jo — Oct 21, 2026 → Oct 21, 2026
- ns4.jdcs.jo — Oct 20, 2026 → Oct 21, 2026
- ns3.jdcs.jo — Oct 20, 2026 → Oct 20, 2026
- ns4.jdcs.jo — Oct 19, 2026 → Oct 20, 2026
- ns3.jdcs.jo — Oct 16, 2026 → Oct 19, 2026
- ns4.jdcs.jo — Oct 15, 2026 → Oct 16, 2026
- ns3.jdcs.jo — Oct 15, 2026 → Oct 15, 2026
- ns4.jdcs.jo — Oct 12, 2026 → Oct 15, 2026
- ns3.jdcs.jo — Oct 9, 2026 → Oct 12, 2026
- ns4.jdcs.jo — Oct 8, 2026 → Oct 9, 2026
- ns3.jdcs.jo — Oct 7, 2026 → Oct 8, 2026
- ns4.jdcs.jo — Oct 6, 2026 → Oct 7, 2026
- ns3.jdcs.jo — Oct 6, 2026 → Oct 6, 2026
- ns4.jdcs.jo — Oct 5, 2026 → Oct 6, 2026
- ns3.jdcs.jo — Oct 4, 2026 → Oct 5, 2026
- ns4.jdcs.jo — Oct 2, 2026 → Oct 4, 2026
- ns3.jdcs.jo — Oct 1, 2026 → Oct 2, 2026
- ns4.jdcs.jo — Sep 30, 2026 → Oct 1, 2026
- ns3.jdcs.jo — Sep 30, 2026 → Sep 30, 2026
- ns4.jdcs.jo — Sep 28, 2026 → Sep 30, 2026
- ns3.jdcs.jo — Jul 6, 2026 → Sep 28, 2026
- ns4.jdcs.jo — Jul 3, 2026 → Jul 6, 2026
- ns3.jdcs.jo — Jul 1, 2026 → Jul 3, 2026
- ns4.jdcs.jo — Jun 30, 2026 → Jul 1, 2026
- ns3.jdcs.jo — Jun 26, 2026 → Jun 30, 2026
- ns4.jdcs.jo — Jun 23, 2026 → Jun 26, 2026
- ns3.jdcs.jo — Jun 23, 2026 → Jun 23, 2026
- ns4.jdcs.jo — Jun 19, 2026 → Jun 23, 2026
- ns3.jdcs.jo — Jun 15, 2026 → Jun 19, 2026
- ns4.jdcs.jo — Jun 12, 2026 → Jun 15, 2026
Network Allocation for 80.90.160.54
- CIDR range
- 80.90.160.0/20
- IP range (int)
- 1,348,116,480 — 1,348,120,575
- Prefix length
- /20
- Organization
- Jordanian mobile phone services Ltd
- ASN
- AS48832
- ASN name
- Jordanian mobile phone services Ltd
- Location
- Amman, Amman Governorate, Jordan
- Coordinates
- 31.955500, 35.943500
- Accuracy radius
- 20 km
- Regional Internet Registry
- RIPE
- Allocated
- 2001-09-07
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-27 04:07:29
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 80.90.160.54?
80.90.160.54 is allocated to Jordanian mobile phone services Ltd (AS48832), registered in Amman, Jordan.
Where is 80.90.160.54 located?
The geolocation for 80.90.160.54 maps to Amman, Jordan 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 80.90.160.54 on?
80.90.160.54 belongs to the 80.90.160.0/20 network block announced by AS48832. This range contains 4,096 addresses.
Does 80.90.160.54 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.