The nonce of an account is not directly accessible through the EVM. In general, the state of arbitrary accounts is not accessible within the EVM.
One (costly and cumbersome) way to prove that an account has a nonce of X at some past block is to give a merkle proof of the account state at that block. Since the nonce is part of the account state you will need to give several (patricia) merkle proofs, one to prove that the nonce is correct for some account state hash, then one to show that that account state is in some state tree, then finally one to show that the root is correct for some block hash.
This will be somewhat difficult to implement and quite costly. Also, it will not detect changes in account nonce during the same block that the transaction is executed.
On the whole, I do not see any good reason why a contract would need to know the nonce of an account. I think you need to conider why you need this information and whether tracking a separate nonce inside your contract would be a better solution.