SQL Server 2017 Enterprise, DB has suspect_pages, GAM and SGAM NOT ALLOCATED - am I OK?
To quote Paul Randal on the matter:


  We’re interested in the output beginning Metadata:. Those fields are
  not stored on the page itself...
  
  If you see the ObjectId is 0, that means there was no metadata found.
  This could be because:
  
  
  The table that the page was part of has been deleted since the page
  corruption was logged 
  The system catalogs are corrupt in some way 
  The
  page is corrupt and so incorrect values were used to look up the
  metadata
  
  
  In any case, you’ll need to wait for DBCC CHECKDB to complete to know the extent of the damage.


It doesn't sound like you're in the clear, so I'd probably push on getting a suitable environment to check a full backup on.