How are you encrypting them? For example, if you're using gpg
, the file command recognises the encryption format (and can even distinguish between ASCII-armoured and non-armoured output):
[madhatta@risby tmp]$ ls -la > foo
[madhatta@risby tmp]$ gpg -e -r fred foo
[madhatta@risby tmp]$ gpg -e -r fred --no-armor foo
[madhatta@risby tmp]$ file foo foo.asc foo.gpg
foo: ASCII text
foo.asc: PGP message
foo.gpg: GPG encrypted data
Edit: I think I see what you're asking for, but I don't much see the point. Assuming that you could somehow set up a certificating authority which recognised every file, and issue some sort of certificate of "encryptedness", how would you use it? To identify the file which it certified with any reliability, it'd have to include a checksum of some kind, and to evaluate that checksum, you'd have to get the original file. Better to just get the original file, and evaluate that.
Sure, you could embed pathnames in the certificates, but then each certificate would have to be checked against a real-time CRL, to avoid people simply decrypting a file in situ and leaving the old certificate in place; and some other system would have to constantly police file changes and update that CRL. No, if you want to do this remotely, may I suggest:
ssh server file foo.asc