Sql-server – Do I face corruption issues

I have found out the msdb.dbo.suspect_pages has 15 entries. 14 of those are last updated in 2014 and of type 7 ("Deallocated").
One entry is of type 1 (823 or 824 error) with a count of 1 and last udpated in June 2015.

Last DBCC CheckDB was ran on Nov. 9th using a maintenance plan. The only output I have is the history of this job saying it completed 100%:

Microsoft (R) SQL Server Execute Package Utility Version
10.50.6000.34 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 7:54:37 PM Progress: 2016-11-09
19:54:44.66 Source: {84CA0A16-9095-4D9D-9CF8-4AF8A1144015}
Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE
msdb..sp…".: 100% complete End Progress Progress: 2016-11-09
19:54:47.22 Source: Check Database Integrity Executing query
"USE [dbname] ".: 50% complete End Progress Progress: 2016-11-09
22:08:15.87 Source: Check Database Integrity Executing query
"DBCC CHECKDB(N'dbname') WITH NO_INFOM…".: 100% complete End
Progress DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 7:54:37 PM Finished: 10:08:16 PM Elapsed: 8018.92
seconds. The package executed successfully. The step succeeded.

So there is not further detailed information about the possible corruption's source / table / index. I am not sure if we found any issues here or not jsut because it completed 100%…

I ran "sp_blitz" and "sp_blitzindex" but it did not return any corruption or something like that.

So far there were no suspect failures or anything that maybe caused by corruption. Since it is there for many months I'm not sure if any action must be taken. Of course there are no backup existing prior that date…

I wonder where to look at next?

Edit:

Another run of DBCC Checkdb as indicated by @Randolph returned the following:

Message
DBCC CHECKDB (myDBName) WITH all_errormsgs, no_infomsgs, data_purity executed by NT AUTHORITY\SYSTEM found 0 errors and repaired 0 errors. Elapsed time: 1 hours 23 minutes 27 seconds. Internal database snapshot has split point LSN = 007c5657:00000372:000e and first LSN = 007c5657:00000353:0001.

Are we okay? Should I delete the entries from msdb.dbo.suspect_pages ?