I'm assuming you want to make sure the file wasn't inadvertently corrupted (rather than concerned about it being deliberately modified in a man-in-the-middle attack).
You'll likely have some difficulty finding the MD5SUM for the file. If it were a day older than what's on the server, you might find it on a mirror, but this is several days old.
What you should instead do is boot from it, hold down shift, and select Check disc for defects. This will give you the same information. (Unless it won't boot or won't get to that point--then it won't give you that information.)
It's fine if it's a USB flash drive, Check disc for defects still works properly (except for being confusingly named).
But why are you using a daily build of a release two versions older than the current daily builds? Perhaps if you provide more detail in your question about what you're trying to achieve, better solutions could be given.